X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com Subject: Re: git stopped working with 1.7.1 In-reply-to: <4B477CDE.7060000@byu.net> References: <21394.1261962819@gemini.franz.com> <20091228042329.GC12367@ednor.casa.cgf.cx> <10362.1262973686@gemini.franz.com> <4B477CDE.7060000@byu.net> Comments: In-reply-to Eric Blake message dated "Fri, 08 Jan 2010 11:43:42 -0700." Date: Mon, 11 Jan 2010 09:55:27 -0800 Message-ID: <6855.1263232527@gemini.franz.com> From: Kevin Layer X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Eric Blake wrote: >> Yes, as maintainer of the git package on cygwin, I've seen sporadic >> failures of the git protocol, which I have always ended up working around >> by switching over to an http protocol. I'm assuming that it might either >> be BLODA or an actual bug in cygwin1.dll regarding handling of socket fds >> across forks, but haven't ever been bothered by it enough to try and debug >> it, because the workaround of http always works. Also, given that other versions of SSH work with the 1.7 git, I would think this is pretty good evidence that it's a bug in cygwin1.dll. Date: Thu, 31 Dec 2009 14:04:16 -0500 Message-ID: <6ee4c8380912311104i1869d73dk818e041f2d8b29ae@mail.gmail.com> Subject: Re: git stopped working with 1.7.1 From: "Brian L." To: cygwin@cygwin.com ... The problem seems to be rooted in cygwin's openssh package. If I point GIT_SSH at plink.exe (from the putty distribution) and configure pageant properly for keyless login then git works fine. -- 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