X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.4 required=5.0	tests=AWL,BAYES_50,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
Subject: Re: git stopped working with 1.7.1
In-reply-to: <4B997742.2000600@redhat.com>
References: <10711 DOT 1261594527 AT gemini DOT franz DOT com> <27300928 DOT post AT talk DOT nabble DOT com> <4B5D7DDF DOT 6070904 AT gmx DOT de> <6ee4c8381002121948x2a0a48fci7918eae743cc03c8 AT mail DOT gmail DOT com> <26824 DOT 1268333412 AT gemini DOT franz DOT com> <4B9976C5 DOT 8030101 AT cwilson DOT fastmail DOT fm> <4B997742 DOT 2000600 AT redhat DOT com>
Comments: In-reply-to Eric Blake <eblake AT redhat DOT com>   message dated "Thu, 11 Mar 2010 16:05:38 -0700."
Date: Mon, 27 Sep 2010 09:38:08 -0700
Message-ID: <17978.1285605488@gemini.franz.com>
From: Kevin Layer <layer AT franz DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Eric Blake <eblake AT redhat DOT com> wrote:

>> On 03/11/2010 04:03 PM, Charles Wilson wrote:
>> >> If it is not being worked on... I agree with Brian.  This is a serious
>> >> impediment to using Cygwin 1.7.  I would think it would be of top
>> >> priority.
>> > 
>> > Only people who experience the problem can diagnose, debug, and fix it.
>> > git works fine for me under cygwin-1.7.1 (Vista, NTFS), so...
>> > 
>> > Has the cygwin git maintainer been able to verify/reproduce the error?
>> > If not, then there's no way he can help you.
>> 
>> I have sometimes seen the problem, but it has never been a show-stopper
>> for me (I fall back to http cloning), and, so far, it has not percolated
>> high enough to the top of my TODO list to be worth the investment of my
>> time on it.

I notice it is still broken (as of last week when I updated to the
latest versions of everything and tested it).

Any further news on when will be fixed?

As for it not being a show-stopper for you, I just want to point out
that there are many of us out here that do not have the luxury of
switching to HTTP cloning when this fails.  So, for us, it's a
show-stopper that requires us to use putty to use git at all.

Thanks.

Kevin

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