X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-5.8 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_YG
X-Spam-Check-By: sourceware.org
X-Received: by 10.15.43.132 with SMTP id x4mr27679384eev.31.1363431150649;        Sat, 16 Mar 2013 03:52:30 -0700 (PDT)
Message-ID: <51444EE8.2030404@gmail.com>
Date: Sat, 16 Mar 2013 11:52:24 +0100
From: marco atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: git fork failure on pull with a workaround (hopefully a clue for a fix)
References: <509AB02F DOT 1000300 AT kitware DOT com> <509AC4E0 DOT 2080709 AT bopp DOT net> <509BC18E DOT 1050905 AT kitware DOT com> <20121123114127 DOT GO17347 AT calimero DOT vinschen DOT de> <1429797465 DOT 20121123163258 AT mtu-net DOT ru> <20121123131123 DOT GS17347 AT calimero DOT vinschen DOT de> <20121123134628 DOT GA32195 AT ednor DOT casa DOT cgf DOT cx> <269536431 DOT 20121123190857 AT mtu-net DOT ru> <1363429864810-96987 DOT post AT n5 DOT nabble DOT com>
In-Reply-To: <1363429864810-96987.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

On 3/16/2013 11:31 AM, CraigMurray wrote:
> I'm getting this now, I get it not just on git pull but also on git branch,
> git status, and others.  I've got a script that gives me status on a series
> of repos and the for failure happens perhaps 1 in 10 repos that are
> inspected.  If I do a series of git pulls, it happens constantly.
>
> The bug started showing up for me tonight for the first time, and now it's
> happening all the time.  I didnt change anything about my environment or my
> cygwin install, was just doing normal work.
>
> I tried those various "shorten your path" workarounds with zero success,
> they did not change my failure rate at all.
>

if nothing is changed on cygwin, unlikely it is a cygwin fault : BLODA ?

anyway:
> Problem reports:       http://cygwin.com/problems.html

specifically:
"Run cygcheck -s -v -r > cygcheck.out and include that file as an 
attachment in your report. Please do not compress or otherwise encode 
the output. Just attach it as a straight text file so that it can be 
easily viewed."

Regards
Marco


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