Le 10/07/2015 0:48, Jeff King a écrit :
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?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html