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

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

From
John Tapsell <johnflux@gmail.com>
Date
Mar 4, 2009, 15:37 UTC
Message-ID
<1236181026-15385-1-git-send-email-johnflux@gmail.com>
---
 http-push.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/http-push.c b/http-push.c
index 30d2d34..6666956 100644
--- a/http-push.c
+++ b/http-push.c
@@ -2293,7 +2293,7 @@ int main(int argc, char **argv)
 		if (info_ref_lock)
 			remote->can_update_info_refs = 1;
 		else {
-			fprintf(stderr, "Error: cannot lock existing info/refs\n");
+			error("cannot lock existing info/refs on remote server\nPerhaps the server is currently busy, or your ~/.netrc file is not configured correctly.");
 			rc = 1;
 			goto cleanup;
 		}
-- 
1.6.2.rc2.23.g77740
Next: Clemens Buchacher
Message 1 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.