From: Vince Rice <vrice@solidrocksystems.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: GitForWindows vs. Cygwin
Date: Wed, 21 Mar 2018 14:37:00 -0000 [thread overview]
Message-ID: <3257113F-24F1-413E-B5F0-25AA36115872@solidrocksystems.com> (raw)
In-Reply-To: <f083bd0e-89f4-8ada-1018-8929dcceed5c@towo.net>
> On Mar 21, 2018, at 3:49 AM, Thomas Wolff wrote:
>
> On 21.03.2018 05:02, Vince Rice wrote:
>>> On Mar 20, 2018, at 7:24 PM, 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.
>> 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.
(And I just realized I quoted an email address last time. My apologies.)
--
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
next prev parent reply other threads:[~2018-03-21 14:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 23:22 KARL BOTTS
2018-03-20 23:50 ` Steven Penny
2018-03-21 0:25 ` Andrey Repin
2018-03-21 4:02 ` Tony Kelman
2018-03-21 4:12 ` Vince Rice
2018-03-21 8:54 ` Thomas Wolff
2018-03-21 14:26 ` cyg Simple
2018-03-21 14:37 ` Vince Rice [this message]
2018-03-21 17:36 ` Tony Kelman
2018-03-21 18:11 ` Tony Kelman
2018-03-21 18:40 ` Brian Inglis
2018-03-22 11:37 ` David Macek
2018-03-21 10:28 ` Frank Fesevur
2018-03-21 18:47 ` Achim Gratz
2018-03-21 23:20 ` Dan Kegel
2018-03-22 16:50 ` R0b0t1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3257113F-24F1-413E-B5F0-25AA36115872@solidrocksystems.com \
--to=vrice@solidrocksystems.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).