From: Jay Soffian <jaysoffian@gmail.com>
To: git <git@vger.kernel.org>
Subject: failed to lock
Date: Wed, 14 Apr 2010 16:49:09 -0400 [thread overview]
Message-ID: <j2o76718491004141349l53b53347v7f4c0edcab69e4c2@mail.gmail.com> (raw)
With git-1.7, I regularly get this when pushing to a non-bare repo:
remote: error: failed to lock refs/remotes/origin/master
...
! [remote rejected] origin/master -> origin/master (failed to lock)
error: failed to push some refs to 'ssh://remote/repo'
I see this pushing from a Mac, to either a Mac or to Cygwin. I have
seen it on various versions of the 1.7 series and possibly before. In
the instance above:
local git version 1.7.0.3.436.g2b878
remote git version 1.7.0.3
In addition, the ref is (apparently) updated just fine. If I push a
second time, no update occurs.
The problem is reproducible. Any idea where I should start debugging it?
j.
next reply other threads:[~2010-04-14 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 20:49 Jay Soffian [this message]
2010-04-14 21:02 ` failed to lock Jay Soffian
2010-04-15 4:00 ` Jay Soffian
2010-04-15 19:00 ` Junio C Hamano
2010-04-15 19:13 ` Jay Soffian
2010-04-15 22:27 ` Junio C Hamano
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=j2o76718491004141349l53b53347v7f4c0edcab69e4c2@mail.gmail.com \
--to=jaysoffian@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).