This is the mail archive of the
mailing list for the Cygwin project.
Re: GitForWindows vs. Cygwin
>>>>>> Can anyone enlighten me about the relationship of "Git for Windows" to Cygwin?
>>>>> They are not related.
>>>> Yes, they are.
>>> No they're not.
>> Tony explained well how they are related; Git for Windows is compiled in and packaged with MSYS2 which is forked from Cygwin.
> No, Tony explained how it's related to MSYS2. This isn't a MSYS2 mailing list.
Don't think they have one. Git for Windows does, and somewhere like
would have been a pretty good alternate place to ask this question.
But I also explained how MSYS2 is very closely related to Cygwin,
and pretending they are completely unrelated and have nothing to do
with one another is myopic and misleading. If "how are MSYS2 and
Cygwin related to one another" is a banned question on this list,
perhaps that should be written down somewhere.
>>> It doesn't use cygwin, therefore it's not related. Since this is a cygwin mailing list,
>>> that means the first two replies were correct — this isn't the place to discuss it.
> Which means this still applies.
When the vast majority of the code in the MSYS2 runtime is exactly
the same as the code in the Cygwin runtime, and Git for Windows uses
msys-2.0.dll in a number of places (which is essentially a renamed
copy of cygwin1.dll) the question was fair. Particularly given Cygwin
has its own git package, it's only natural to wonder how that differs
from Git for Windows, and how it differs from the probably lesser-
known msys2-git package (which is built in very nearly the same
configuration as the Cygwin git package, posix style).
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple