From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: snapshot 2013-01-23
Date: Thu, 31 Jan 2013 08:45:00 -0000 [thread overview]
Message-ID: <loom.20130131T092800-978@post.gmane.org> (raw)
In-Reply-To: <20130131053627.GB4914@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2013-01-31 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 13:59 Achim Gratz
2013-01-28 14:57 ` Achim Gratz
2013-01-29 12:47 ` Achim Gratz
2013-01-30 11:28 ` Achim Gratz
2013-01-31 5:37 ` Christopher Faylor
2013-01-31 8:45 ` Achim Gratz [this message]
2013-01-29 10:45 ` Achim Gratz
2013-01-31 5:35 ` Christopher Faylor
2013-01-31 9:48 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20130131T092800-978@post.gmane.org \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).