From: Andrey Repin <anrdaemon@yandex.ru>
To: "KARL BOTTS" <kdbotts@usa.net>, cygwin@cygwin.com
Subject: Re: GitForWindows vs. Cygwin
Date: Wed, 21 Mar 2018 00:25:00 -0000 [thread overview]
Message-ID: <324994357.20180321024235@yandex.ru> (raw)
In-Reply-To: <587wcTwzy5968Set.1521586344@web02.cms.usa.net>
Greetings, KARL BOTTS!
> Can anyone enlighten me about the relationship of "Git for Windows" to
> Cygwin?
They are not related.
> I have no intention to use GFW myself: I use Cygwin git. But now other people
> around here are discovering GitHub, MSysGit and or GitForWindows. Pretty
> soon, we are going to wind up with multiple git flavors installed on the same
> host, which worries me.
Erm, but how?
> But now I hear of this GitForWindows thing. Which seems to have replaced
> MSysGit, with a GUI thrown in. But is it _still_ a stale fork of Cygwin, or a
> fork at all? Is it descended from MSysGit? I have been googling all over,
> but not finding good answers.
You'd have better chance for the answers at their support channels.
--
With best regards,
Andrey Repin
Wednesday, March 21, 2018 02:40:11
Sorry for my terrible english...
--
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-20 23:50 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 [this message]
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
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=324994357.20180321024235@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=kdbotts@usa.net \
/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).