X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.4 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com Subject: Re: "git clone" over ssh fails intermittently w/snapshot 20120123 In-reply-to: <26758.1327703355@freon.franz.com> References: <26758.1327703355@freon.franz.com> Comments: In-reply-to Kevin Layer message dated "Fri, 27 Jan 2012 14:29:15 -0800." Date: Fri, 27 Jan 2012 14:32:54 -0800 Message-ID: <26967.1327703574@freon.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 I don't know what happened to the email in transit, but much information at the head of the email was chopped off. From my outbox, here's the missing bit: ***************** This is the failure mode: $ rm -fr test; git clone git:/repo/git/composer test Cloning into test... fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed $ That is not using the git protocol. The machine is called `git'. It fails most of the time, but it definitely works sometimes, and even has stretches of successes. At first, I thought it was isolated to large repos, but it definitely happened on some smaller ones. -- 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