Date: Mon, 27 Sep 2010 15:59:50 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: git stopped working with 1.7.1
Message-ID: <20100927195950.GB22191@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT 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> <17978 DOT 1285605488 AT gemini DOT franz DOT com> <4CA0E145 DOT 8030204 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CA0E145.8030204@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Sep 27, 2010 at 02:24:05PM -0400, Bill Hoffman wrote:
>On 9/27/2010 12:38 PM, Kevin Layer wrote:
>> 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.
>>
>I came up with a way to reproduce this if a developer wanted to try and 
>fix it.
>
>That post can be seen here:
>http://cygwin.com/ml/cygwin/2010-07/msg00506.html
>
>git/ssh on cygwin are pretty much broken at this point...

And, when I tried this, it pointed to an actual problem in git rather than
a problem in Cygwin so that limits what is meant by "developer".

Isn't git normally used for source control management by programmers?
If this is such a bad problem why isn't one of those programmers looking
into it and proposing a fix?  That's one of the reasons for free
software - you can fix the problems yourself.

And, before someone inevitably opines that I'm just being mean, I have
to point out that this really is how many open source projects work.
People who are not maintainers actually do propose fixes.

cgf

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