X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_CG
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Achim Gratz <Stromeko AT NexGo DOT DE>
Subject:	Re: snapshot 2013-01-23
Date:	Thu, 31 Jan 2013 08:44:30 +0000 (UTC)
Lines:	26
Message-ID:	<loom.20130131T092800-978@post.gmane.org>
References:	<loom DOT 20130128T145147-619 AT post DOT gmane DOT org> <loom DOT 20130128T155528-999 AT post DOT gmane DOT org> <loom DOT 20130129T133921-844 AT post DOT gmane DOT org> <loom DOT 20130130T122610-807 AT post DOT gmane DOT org> <20130131053627 DOT GB4914 AT ednor DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
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

Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:
> I can't duplicate this with a simple "git pull".  Could you provide the
> exact sequence of steps needed to duplicate the problem?

In origin, roll back and then advance HEAD (by rewriting or amending some
commits), then try to pull this in the downstream repo so that it needs to do a
forced update.  The downstream repo is on an FS that I have to mount with
"noacl" because I am not allowed to change any ACL there:

//server/repo on /mnt/repo type netapp (binary,noacl,user,bind)

The hang apparently happens when the HEAD rewind is about to happen.

Originally I couldn't even read the ACL on that volume, but it seems that this
has been changed that I complained about it.  IT did tell me they'd do nothing,
but it looks they changed their mind, without telling me of course.  This change
must have happened quite recently and it is quite possible that this was when
the failures started (which did not happen again since I've changed the Git
config to include filemode=false for this repo).

Anyway, I now think it's not related to any snapshot, even if it might warrant
further investigation.


Regards,
Achim.


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

- Raw text -