Re: [PATCH] check_and_freshen_file: fix reversed success-check
- From
- X H <music_is_live_lg@hotmail.com>
- Date
- Jul 11, 2015, 22:21 UTC
- Message-ID
- <BLU437-SMTP311678316C434857657D6BF69E0@phx.gbl>
- In-Reply-To
- <20150709224830.GA24998@peff.net>
Le 10/07/2015 0:48, Jeff King a écrit :
Show 16 quoted lines
> On Thu, Jul 09, 2015 at 10:51:50PM +0200, Johannes Sixt wrote: > >>> Ah! That code is less than a year old. When I began to adopt a workflow >>> requiring force-pushes lately, I wondered why I haven't seen these >>> failures earlier, because I did do force pushes in the past, but not >>> that frequently. I thought that I had just been lucky. But this would >>> explain it. >> >> And, in fact, with this patch these particular failures are gone! Thank you >> so much! > > Great, thanks for testing. You can temper your appreciation by noticing > that I introduced the bug in the first place. ;) > > -Peff >
Hi,
Thank you for the patch. I hope it will solve the problem and permit to have a second user using the same repository.
How are the permission handled, is it git that is asking to create a file read only or rw on the remote or is it the environment with umask ans so on that decides it, or Windows when the drive is mounted with noacl?