From: John Tapsell <johnflux@gmail.com>
To: git@vger.kernel.org
Cc: John Tapsell <johnflux@gmail.com>
Subject: [PATCH] Clarify the "cannot lock existing info/refs" error
Date: Wed, 4 Mar 2009 15:37:06 +0000 [thread overview]
Message-ID: <1236181026-15385-1-git-send-email-johnflux@gmail.com> (raw)
---
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 reply other threads:[~2009-03-04 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 15:37 John Tapsell [this message]
2009-03-04 19:28 ` [PATCH] Clarify the "cannot lock existing info/refs" error Clemens Buchacher
2009-03-05 8:00 ` John Tapsell
2009-03-05 8:50 ` Clemens Buchacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1236181026-15385-1-git-send-email-johnflux@gmail.com \
--to=johnflux@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).