X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 24 Feb 2009 11:38:09 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Git broken with cygwin-1.7 Message-ID: <20090224163809.GC16741@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <49A3F88B.9090305@byu.net> <49A3F939.4020901@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A3F939.4020901@byu.net> User-Agent: Mutt/1.5.16 (2007-06-09) 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 On Tue, Feb 24, 2009 at 06:42:17AM -0700, Eric Blake wrote: >According to Eric Blake on 2/24/2009 6:39 AM: >>You can work around this by cloning via http protocol instead of git. >>I have seen occasional read errors as well, but have had a hard time >>reliably reproducing them. I guess it's a good thing to report that >>your sample failed in the same place for me. > >Phooey - it passes under strace. I hate finding heisenbugs. Have you tried: strace -b1000000 ... I added that buffering capability because it sometimes help find this type of problem. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/