Re: [PATCH/RFC 0/7] Multiple simultaneously locked ref updates

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 29, 2013, 16:21 UTC
Message-ID: <xmqq7gf479jm.fsf@gitster.dls.corp.google.com>
In-Reply-To: <521F6CF0.6040905@kitware.com>

Brad King <brad.king@kitware.com> writes:

> Nor should it in this case.  I was saying that the front-end
> needs to reject duplicate ref names from the stdin lines before
> trying to lock the ref twice to avoid this message.

How about trying not to feed duplicates?

$ 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.