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:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=nq+1fVtDxqbR2pORCUJMSTosa/vFRvfbithedqzk2kV6MQ8e0HUZy
	niaFSJiEt+mPVYHWabxxKX9Nl3Tc/abbv/Jmrjnv10qurGAtsoKAyU03RLWjNbXH
	zFLqkGPVuYO0F/Lr8NTq4hQYyM8ZtljFYQZefbeW3CKET3Q3iu7pP8=
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:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=Yf6CaQxGqWStNpr+5skwcPYiJCU=; b=VCT4aWSnSECaEffcNbl3Rj+BOYYl
	uK2RMvvW8hHY3zdE2eGjalS8y/FY+QJ88BoP2CYjjFu+UTq55jjsYy/1wrP3cR9+
	lGiTCp6ViOhvrjD8/HpAK9R/JvPsiUYIroWBLxGbg4y7K6PBnmlY6KU+J3AuPv4u
	8qSQNls+XasNE0s=
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-Spam-SWARE-Status:	No, score=-1.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/Ruit/WEHdv7oQT6mTBk2V
Date:	Thu, 6 Feb 2014 15:14:13 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin SSH and msysGit
Message-ID:	<20140206201413.GB5851@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CABeoYThy8qrE3zVpj8z-R5-ng4AtADr85jrMGAM0EwftbJ_m7w AT mail DOT gmail DOT com> <431017993 DOT 20140206013913 AT mtu-net DOT ru> <CABeoYTgU3sUiz+Xf-dxtLRnW3eiOii3MbYX1q70Uti6Myg3tyA AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CABeoYTgU3sUiz+Xf-dxtLRnW3eiOii3MbYX1q70Uti6Myg3tyA@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Feb 06, 2014 at 09:46:50PM +0200, Someone Somebody wrote:
> I did some additional research of my own, it seems that the only
>thing that should really be os dependent is in the working dir and the
>index file and since this is not relevant for pure push/fetch I think
>it might work ok using Cygwin's Git.
>
>But who knows... msysGit includes a lot of different patches to get it
>to work well in Windows and many of them are not merged into the core
>Git and who knows really whether one of them can affects this.
>
>Also I think trying to add msysGit after the Cygwin $PATH might still
>have something explode since the binaries in the libexec/git-core are
>dependent on dlls in the bin directory... and they might have similar
>names to Cygwin binaries and having the Cygwin dlls earlier in the
>$PATH might cause it to bomb. (Git seems to invoke "git-receive-pack",
>"git-upload-pack" vs "git receive-pack", "git upload-pack" requiring
>the libexec/git-core directory).
>
>I might just have to ask on the msysGit mailing list :P

As MSYS is actually a competing project, we don't support any MSYS
utilities here and aren't terribly interested in hearing about
interaction problems with Cygwin.  So asking for help there is probably
for the best, although you could have the same problem in reverse.

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