X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: snapshot 2013-01-23 Date: Tue, 29 Jan 2013 12:47:09 +0000 (UTC) Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Achim Gratz NexGo.DE> writes: > Git apparently has similar problems when it is started from Emacs (via magit). Part of the problem has been solved by rolling back to the 2013-01-07 snapshot. I still get Git to hang up when doing a pull that results in a forced update on a worktree that is mounted with "noacl" option. Interestingly, when I do: git gc --aggressive git remote update git pull instead of simply: git pull then everything seems to work. I do not have that problem with the same worktree when instantiated on a volume where "noacl" does not have to be used, so somehow it must have something to do with Git waiting for the results of a chmod or similar change to the FS becoming visible (which then never happens because the access rights are fake). 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