From: Clemens Buchacher <drizzd@aon.at>
To: John Tapsell <johnflux@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarify the "cannot lock existing info/refs" error
Date: Wed, 4 Mar 2009 20:28:53 +0100 [thread overview]
Message-ID: <20090304192853.GA10567@localhost> (raw)
In-Reply-To: <1236181026-15385-1-git-send-email-johnflux@gmail.com>
On Wed, Mar 04, 2009 at 03:37:06PM +0000, John Tapsell wrote:
> -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.");
In my experience this is usually caused by http-push crashing and leaving
stale locks behind until it times out after 10 minutes. I don't think we
should speculate here unless we can narrow down the error condition.
next prev parent reply other threads:[~2009-03-04 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 15:37 [PATCH] Clarify the "cannot lock existing info/refs" error John Tapsell
2009-03-04 19:28 ` Clemens Buchacher [this message]
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=20090304192853.GA10567@localhost \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.