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:date:from:to:subject:mime-version:message-id
	:content-type:content-transfer-encoding; q=dns; s=default; b=APp
	unZeCXWRrsGEyfIeksUCd4Vm58mYuZeqrb/c2GXK5IX4wOZ4BUoLIGW9Uu1hPXH1
	A+uw/nHWDlN0addAbJa9MLiERkArEQKFCmJCXYiQhf7BRncJnt8ODIkTSBh9d6ow
	OyWZSUrgbXRPf+iPGjZ03mF9Qmoc55+3cF9PPMSk=
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:date:from:to:subject:mime-version:message-id
	:content-type:content-transfer-encoding; s=default; bh=YwypSQtjm
	NlcpANey/irn1RFekY=; b=dy2M6ejZRuffgHguWYeTvkA29k9N0dxbRioSJrqwS
	4Z67XFKZeYraUa4346Yvo7JQqHQ0V8h2VbRo4GCfes6oxh6let+4ztVgZv2oQi0m
	RJqVOtydHWL7bxCpTHpapPbp2Kktk48iTfLJyZmoeOBp+6XQVvp41DGQu6b04f/0
	u0=
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=-5.5 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_PASS autolearn=ham version=3.3.2 spammy=H*c:ISO-8859-1, HOME, Hx-languages-length:1144, watch
X-HELO:	co01.mbox.net
X-USANET-Received:	from co01.mbox.net [127.0.0.1] by co01.mbox.net via mtad (C8.MAIN.4.10L) with ESMTP id 289wcTw1y3216M01; Tue, 20 Mar 2018 22:52:24 -0000
X-USANET-Routed:	3 gwsout-vs Q:bmvirus
X-USANET-Routed:	3 gwsout-vs Q:bmvirus
X-USANET-GWS2-Tenant:	usa.net
X-USANET-GWS2-Tagid:	UNKN
X-USANET-Source:	165.212.11.131 OUT kdbotts AT usa DOT net ca31.cms.usa.net CLR
X-USANET-MsgId:	XID289wcTw1y9086X01
X-USANET-Auth:	165.212.8.202 AUTO kdbotts AT usa DOT net web02.cms.usa.net CLR
Date:	Tue, 20 Mar 2018 17:52:24 -0500
From:	"KARL BOTTS" <kdbotts AT usa DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	GitForWindows vs. Cygwin
Mime-Version:	1.0
Message-ID:	<587wcTwzy5968Set.1521586344@web02.cms.usa.net>
Z-USANET-MsgId:	XID106wcTw1y7680X31
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id w2KMqgg8000709

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 AT usa DOT 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

- Raw text -