public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: GitForWindows vs. Cygwin
Date: Tue, 20 Mar 2018 23:22:00 -0000	[thread overview]
Message-ID: <587wcTwzy5968Set.1521586344@web02.cms.usa.net> (raw)


Can anyone enlighten me about the relationship of "Git for Windows" to
Cygwin?

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.

I know that MSysGit is basically a stale fork of Cygwin.  I tried it a long
time ago (during a period when the git in Cygwin was not getting updated
often), and it caused me trouble.  As I recall, the bash in it was only v3,
and I was used to v4, and some of my scripts didn't run right, and MSysGit
messed up my HOME dir.  Anyhow, I got rid of MSysGit.  And now that the git in
Cygwin is keeping current, I am quite content.

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.

I just want to watch out for the damn thing, and try to keep it away...

---
Karl Botts, kdbotts@usa.net


--
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

             reply	other threads:[~2018-03-20 22:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 23:22 KARL BOTTS [this message]
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
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=587wcTwzy5968Set.1521586344@web02.cms.usa.net \
    --to=kdbotts@usa.net \
    --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).