On Mon, 9 Jan 2017 09:26:15 +0300 Konstantin Khomoutov <[email protected]> wrote:
> On Sun, 8 Jan 2017 09:54:30 -0800 > Michael <[email protected]> wrote: > > > So, the question of "which form to use on windows" depends if you > > are using git for windows with the normal windows shell, or if you > > are using git for windows with cygwin and the bash shell? > > Sounds about correct. "Native" Windows shells should pass wildcards > to Git commands unmodified, and Git will take care of their > expansions by itself. Well, there's yet one more point I forgot to formulate while having it on my mind actually. Since Windows port of Git _has to_ deal with the fact Windows shells don't expand fileglobs, it definitely has some layer which deals with command-line processing. A possible issue is that GfW uses MinGW to compile its core components (written in C), and MinGW should supposedly have some means to make non-Windows programs being ported on Windows "feel at home" with regard to parsing commad-line arguments. Hence there might be some layer provided by MinGW which deals with fileglobs before core Git code has a chance to get its hands on them. I don't know for sure how exactly this is currently implemented, so I'd ask on the GfW's mailing list for details. [...] -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
