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

Re: [PATCH] Clarify the "cannot lock existing info/refs" error

From
Clemens Buchacher <drizzd@aon.at>
Date
Mar 5, 2009, 08:50 UTC
Message-ID
<20090305085052.GA24669@localhost>
In-Reply-To
<43d8ce650903050000g4466ab2fne5fb8ed009808346@mail.gmail.com>
On Thu, Mar 05, 2009 at 08:00:37AM +0000, John Tapsell wrote:
> On google I found that people had been getting that error if they have
> the wrong password.
That's easy enough to verify. Using the wrong username/password I get
	error: Cannot access URL $url, return code 22
	error: failed to push some refs to '$url'
which is not very helpful, but otherwise unrelated.
> -fprintf(stderr, "Error: cannot lock existing info/refs\n");
> +error("cannot lock existing info/refs on remote server\n");
That's a less ambiguous but equally unhelpful error message.
Previous: John Tapsell
Message 4 of 4 in “Clarify the "cannot lock existing info/refs" error”
  1. Clarify the "cannot lock existing info/refs" errorJohn Tapsell, Mar 4, 2009
  2. Clemens BuchacherMar 4, 2009
  3. John TapsellMar 5, 2009
  4. Clemens BuchacherMar 5, 2009

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.