From: Jeff King <peff@peff.net>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: git@vger.kernel.org
Subject: Re: Git rebase dies with fatal: Unable to create '.../.git/index.lock': File exists.
Date: Mon, 16 Sep 2013 17:15:01 -0400 [thread overview]
Message-ID: <20130916211501.GA5477@sigill.intra.peff.net> (raw)
In-Reply-To: <20130916182852.GA14513@obsidianresearch.com>
On Mon, Sep 16, 2013 at 12:28:52PM -0600, Jason Gunthorpe wrote:
> I have emacs windows open that have files within the git tree open in
> them. My emacs has vc-git mode loaded and global-auto-revert-mode set.
>
> During the rebase the files open in emacs are changed by git, when
> emacs notices this (which is random with respect to the ongoing
> rebase) it auto reverts and runs git commands (due to vc-git), which
> causes the rebase to randomly fail.
>
> Worse, I've noticed that this also randomly seems to cause the rebase
> to loose a commit if you --continue from that point.
>
> Can git have some retry in the locking so this doesn't happen?
I'm not clear on which git commands are being run. If they are actually
mutating the index, then isn't this more than a lock contention issue?
In other words, "git rebase" is assuming nobody is mucking with the
index while it runs; if emacs is doing so, then the results could be
quite confusing, even if we retried the lock acquisition.
-Peff
next prev parent reply other threads:[~2013-09-16 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 18:28 Git rebase dies with fatal: Unable to create '.../.git/index.lock': File exists Jason Gunthorpe
2013-09-16 21:15 ` Jeff King [this message]
2013-09-16 21:21 ` Jason Gunthorpe
2013-09-16 21:47 ` Jeff King
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=20130916211501.GA5477@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jgunthorpe@obsidianresearch.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 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).