Hi Hannes, On Mon, 7 Aug 2017, Johannes Sixt wrote: > 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. OpenSSH and GPG are also required for Git for Windows to function well. You may not need them, but others do. Also, you may be content with running the shell in your Windows Console, but most users use MinTTY (and would have used rxvt if we ever had gotten that to work). Given your circumstances, I would estimate that you could already use a BusyBox-based system. You have been traditionally very comfortable with running your own setup, and putting it together yourself, so you could cherry-pick the bits and pieces. The only exception may be `vi`. While BusyBox comes with a `vi` applet, I disabled it because it does not work in MinTTY, and it also offers a far cry from the vim.exe functionality I am used to. So you may want to revert https://github.com/git-for-windows/busybox-w32/commit/4dccf1500f4 and rebuild BusyBox-w32 yourself. Ciao, Dscho
