git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: failed to lock

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2010, 22:27 UTC
Message-ID
<7vbpdkic6p.fsf@alter.siamese.dyndns.org>
In-Reply-To
<k2j76718491004151213xdb223ff8kd43f170eaf3a470a@mail.gmail.com>
Jay Soffian <jaysoffian@gmail.com> 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.

Previous: Jay Soffian
Message 6 of 6 in “failed to lock”
  1. Jay SoffianApr 14, 2010
  2. Jay SoffianApr 14, 2010
  3. Jay SoffianApr 15, 2010
  4. Junio C HamanoApr 15, 2010
  5. Jay SoffianApr 15, 2010
  6. Junio C HamanoApr 15, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.