X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=foaS7IfQsRFCFkjV
	ZyKmWBd/UA5DUt9RJiePP054rmqMTg0ucg7TbY0Gl8byY8TcSq1mnXPzVD3IgRpN
	AAiPi2z3H27jB6LIdmuui3rQzdQpU76exNtHhNxOFTsYFAZknOW5a+p+t2MCm4cU
	awlARzo8B68M7AaJ6rSEpcHDf0E=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=XoKUZDnpCHRB9ZyUW4fTgY
	GRKCo=; b=tBVfm1pLfInZSW/hfqCZkcYVllbQUSUxEQkhkt3CeCwumhQZOshvci
	M5ISdk6jKy1a1CCJMJDjNlI3+Y0thf4HsnqGuPzQBGSldsJ6WItRGf4d6nnwRaIU
	mlBKt+ydnRAdy+tSDjmysRQaVnYzaNgG+a99J6rnON7xH9902OPvI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=calgary, Alberta, inglis, Inglis
X-HELO: smtp-out-no.shaw.ca
X-Authority-Analysis: v=2.3 cv=Tai4SyYh c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=1XWaLZrsAAAA:8 a=wn2tWnfOKRrLvmu7J_sA:9 a=QEXdDO2ut3YA:10
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: GitForWindows vs. Cygwin
To: cygwin AT cygwin DOT com
References: <587wcTwzy5968Set DOT 1521586344 AT web02 DOT cms DOT usa DOT net> <324994357 DOT 20180321024235 AT yandex DOT ru> <DM5PR22MB025047603811CBA882A0DDC4A7AA0 AT DM5PR22MB0250 DOT namprd22 DOT prod DOT outlook DOT com> <C1D56E97-540D-4221-B310-53CC3045A8C0 AT solidrocksystems DOT com> <f083bd0e-89f4-8ada-1018-8929dcceed5c AT towo DOT net> <3257113F-24F1-413E-B5F0-25AA36115872 AT solidrocksystems DOT com> <DM5PR22MB025047482147E78FE9740741A7AA0 AT DM5PR22MB0250 DOT namprd22 DOT prod DOT outlook DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <aac70cf0-725e-6cd1-603e-41c3909745f1@SystematicSw.ab.ca>
Date: Wed, 21 Mar 2018 12:11:50 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <DM5PR22MB025047482147E78FE9740741A7AA0@DM5PR22MB0250.namprd22.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfDALdLhuD3bC8XIg9OrdWLwevpY0ao/oq1LDBF1Zf0+vnHPBeC2jhZe6g2hO4EsicxFmdAM79zNywTgNGZVITxGr5vIR2g3kDz7IVizIkj/LH6r9rg+J Z4xq/S4y8lb0IULsITBMo8Q+5Duzb5wAVUhIr5bexOeHOGMXZXcwlKyb0F383MFCZXkDQyTI0/OOPg==
X-IsSubscribed: yes

On 2018-03-21 11:26, Tony Kelman wrote:
>>>>>>> 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
> https://groups.google.com/forum/#!topic/git-for-windows/jtwpuGa5u_E
> 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).

Only GfW and Msys2 Git projects can answer how Cygwin components are used by
their projects. Most (all?) of Cygwin winsup and (all of?) newlib are available
under permissive BSD(-style) licences that allow all uses of the code.

It's possible that the developers of those GfW and Msys2 Git packages have moved
on from those projects and the current maintainers don't have the basis to answer.

One might expect some of those maintainers to be subscribed to this list and
able to answer, but they may not, and just check web archives, or they may
choose not to get into this discussion here, although they could perhaps suggest
a more appropriate forum, or take the discussion off-list.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple