git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git-for-windows@googlegroups.com, git@vger.kernel.org
Subject: Re: [git-for-windows] [ANNOUNCE] Git for Windows 2.14.0
Date: Mon, 7 Aug 2017 19:31:57 +0200	[thread overview]
Message-ID: <f92fcfeb-75b9-6ee2-0bc0-a42d1dc01ebd@kdbg.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1708071147430.4271@virtualbox>

Am 07.08.2017 um 12:02 schrieb Johannes Schindelin:
> On Sun, 6 Aug 2017, Johannes Sixt wrote:
>> Am 06.08.2017 um 01:00 schrieb Johannes Schindelin:
>>>     * Comes with [BusyBox v1.28.0pre.15857.9480dca7c](https://github.com/
>>>       git-for-windows/busybox-w32/commit/9480dca7c].
>>
>> What is the implication of this addition? I guess it is not just for the
>> fun of it. Does it mean that all POSIX command line tools invoked by Git
>> including a POSIX shell are now routed through busybox instead of the
>> MSYS2 variant?
> 
> As I wrote a little later:
> 
> * Git for Windows releases now also include an experimental [BusyBox-based
>    MinGit](https://github.com/git-for-windows/git/wiki/MinGit#experimental-busybox-based-mingit).

Thanks for the clue. It's an interesting concept. I would be interested 
in replacing my old MSYS environment by BusyBox. At best, it would be 
just a matter of replacing sh.exe.

-- Hannes

  reply	other threads:[~2017-08-07 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05 23:00 [ANNOUNCE] Git for Windows 2.14.0 Johannes Schindelin
2017-08-06  8:34 ` [git-for-windows] " Johannes Sixt
2017-08-07 10:02   ` Johannes Schindelin
2017-08-07 17:31     ` Johannes Sixt [this message]
2017-08-07 19:35       ` Johannes Schindelin
2017-08-06 11:16 ` Lars Schneider
2017-08-07  8:21   ` Konstantin Khomoutov
2017-08-07  9:20     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f92fcfeb-75b9-6ee2-0bc0-a42d1dc01ebd@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).