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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=ShBm+07
	s2UfRraioixK4sEqQXsRLoI/+6qeuhCwnMC1AroE/t/bgjlyEbjVNFLsh3IJd8cu
	ZnjbPsfljjizSXHSNOirEn5QDRm0H08cWLe/9uZ2vhdyNbT510M6OaUu+8+SxQwp
	tGNErHpE+dStvZt9nMUUC3B2XjrovM0Cys74=
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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=W+n8rK+MYn5nP
	eLNm0M7P3t/LEg=; b=JS9GStZfTzptAJ86Hms7Iq9LctSkpBiNuwlZO2ysyefph
	+d8J45PXlVr3+/y9SZWS4htkIiReXt9XWe6uFdBOD2XcRSn4MVeVBKrGGYJbFr2/
	IWcfWlFOMD4OetMRoFBehOLaunooHroU44GPo527ckZ/hQokpZ3Zpne2JyhisU=
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.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=HOME, damn, pieces, watch
X-HELO:	mail-lf0-f46.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=nyCzl8JjpvtlMZ7RLEWZcbNg1TQPHvzNcXywVn1zZ9Q=; b=W5rsy/1cEjg2+AACi/zsHICA51cblw8S8sJdgxx8mHkNSCX6mBdOLJiI05xqpkSUlN 4/dx2aoaQpCnX2zcS7d3AJ3ByrVNnqzQexPrczkYEQ0v3aA5nDEz2hDgP1qfeyd2hkjE AImEjTVrxLKTJuPaXvimqTRIQUMqDSJJm4SZbllvB+MsYeQYNeM5k9xdv748nP7KHxCw HzGgVQdrp0CxM1fjFPd1g9KEdRRTVhXC56jzuezy3E1Iuzb0zcCmqhgT2ypxU/41vipM /DrqNxO3SQsxoV3IbiSZxWoxfj0F04jAypLCt/sCEvyyn7b4KrPEnYZAwnvqrhXDsnq3 9HRA==
X-Gm-Message-State:	AElRT7HzgDCIEY9O/NIZey3YllCsEMP+6WnpOANbDCG/8getlsEBz2hv E+iaKqffgTXvmr9ikBti7EY+r1IULTZnlbrLEbY=
X-Google-Smtp-Source:	AG47ELvlyxNELaE/WgzfJKTmJMuAUrv6nEFfqXDAepB3I/QXRjS4zMdslnBwFOPslXXH/rBKa2G2koYpIoLvXeKfBfI=
X-Received:	by 2002:a19:cfc2:: with SMTP id f185-v6mr14511917lfg.75.1521736398449; Thu, 22 Mar 2018 09:33:18 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<587wcTwzy5968Set.1521586344@web02.cms.usa.net>
References:	<587wcTwzy5968Set DOT 1521586344 AT web02 DOT cms DOT usa DOT net>
From:	R0b0t1 <r030t1 AT gmail DOT com>
Date:	Thu, 22 Mar 2018 11:33:18 -0500
Message-ID:	<CAAD4mYhR63ewCX86ZW_6onTTMQJ8m1OkOkX-aF8ApFR1mTWgeA@mail.gmail.com>
Subject:	Re: GitForWindows vs. Cygwin
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

Hello list, I think there is information the OP can use, but no one
has apparently experienced it. Also, it's not likely he'd have gotten
good information from the other respective mailing lists, so I think
it is fine he asked here.

However, I am not very smart and my opinion does not matter, so I
apologize for the noise on the list.

On Tue, Mar 20, 2018 at 5:52 PM, KARL BOTTS <kdbotts AT usa DOT net> wrote:
>
> 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...
>

What you need to watch out for is having a cluttered PATH. If you
install, say, the WinAVR toolchain, it includes either an MSYS
distribution or select pieces of Cygwin (bundling MSYS[2] is more
popular, from memory). These old tools will cause problems if you try
to run autotools for a native project from within Cygwin. Other
distributions, like the Haskell Stack, have the same problem.

If you install MSYS2 and Cygwin and both are in your path but you keep
both up to date, you won't have this problem.

Cheers,
     R0b0t1

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

- Raw text -