Hi, On Thu, 4 May 2017, ankostis wrote: > On 4 May 2017 at 11:47, Adam Dinwoodie <adam@xxxxxxxxxxxxx> wrote: > > Confirmed: the Cygwin project as a general rule doesn't support this > > sort of mixing of Windows and Cygwin tools. Either use Python and Git > > packages both provided by Cygwin, or both provided by Windows. > > > > Mixing and matching does work sometimes -- as was apparently the case > > with Cygwin Git v2.8.3-1 -- but it requires care and you're generally on > > your own with it. > > MSYS2's git-2.12.1 also works fine, so there must be something > different in this build of git that breaks this long-standing capability. MSYS2's runtime has auto-conversion functionality, trying to guess what arguments passed to a non-MSYS2 program may be Unix paths, converting them to Windows ones. So what you may see here has nothing to do with MSYS2's Git *not* having the change that breaks Cygwin Git for you, but MSYS2's runtime saving you from trouble. > Judging from the error-message, it somehow concatenates input & output > paths. > Isn't this something to research about? It is something to research about. But by you, not by me. I need to focus on bigger-impact issues, because I do not scale, and Git for Windows' users generally do not experience the problem you described. Ciao, Johannes