Re: failed to lock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jay Soffian <jaysoffian@xxxxxxxxx> writes:

> So it seems safer to me that the destination should ignore duplicates
> in the received list.

We probably need it on both ends.

On the receiving end, it probably is a better idea to make verify_lock()
succeed if the ref has already been updated to the value we are going to
update with, as I suspect that the issue is not limited to receive-pack.
It needs some restructuring of lock/verify/commit primitives, though.
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]