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

Re: [PATCH] Remove the requirement opaquelocktoken uri scheme

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 20, 2008, 20:09 UTC
Message-ID
<7vabaqwqv3.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1229753986-5193-1-git-send-email-catap@catap.ru>
"Kirill A. Korinskiy" <catap@catap.ru> writes:
Show 6 quoted lines
> ...
> This resulted in push failure (often resulted in "cannot lock existing
> info/refs" error message) when talking to a server that does not use
> opaquelocktoken URI scheme.
>
> Signed-off-by: Kirill A. Korinskiy <catap@catap.ru>
Thanks.
Previous: Kirill A. Korinskiy
Message 4 of 4 in “Remove the requirement opaquelocktoken uri scheme”
  1. Remove the requirement opaquelocktoken uri schemeKirill A. Korinskiy, Dec 19, 2008
  2. Junio C HamanoDec 19, 2008
  3. Remove the requirement opaquelocktoken uri schemeKirill A. Korinskiy, Dec 20, 2008
  4. Junio C HamanoDec 20, 2008

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.