From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Jeff King <peff@peff.net>
Cc: Phillip Wood <phillip.wood123@gmail.com>,
Elijah Newren <newren@gmail.com>,
phillip.wood@dunelm.org.uk, Duy Nguyen <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Possible race condition with git-rebase + .git/index.lock
Date: Wed, 13 Mar 2019 17:07:19 -0400 [thread overview]
Message-ID: <87lg1i4h6g.fsf@sergiodj.net> (raw)
In-Reply-To: <20190313205926.GB5397@sigill.intra.peff.net> (Jeff King's message of "Wed, 13 Mar 2019 16:59:26 -0400")
On Wednesday, March 13 2019, Jeff King wrote:
> On Wed, Mar 13, 2019 at 04:48:36PM -0400, Sergio Durigan Junior wrote:
>
>> Huh, I do have some of the files opened in Emacs! They're in
>> background, but indeed, now that you mentioned I remember that Emacs
>> keeps track of changes and invokes "git status" sometimes. Next time I
>> see the bug, I'll try closing the files and see if it happens again.
>
> If Emacs (I guess maybe magit?) is running "git status" behind the
> scenes, you might benefit from teaching it to use "git
> --no-optional-locks status" instead. See the section "BACKGROUND
> REFRESH" in "git help status" for more discussion.
Thanks Jeff. That's going to be helpful.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-03-13 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 21:38 Possible race condition with git-rebase + .git/index.lock Sergio Durigan Junior
2019-03-11 22:50 ` Eric Sunshine
2019-03-11 22:53 ` Sergio Durigan Junior
2019-03-12 10:28 ` Duy Nguyen
2019-03-12 16:45 ` Sergio Durigan Junior
2019-03-12 19:23 ` Elijah Newren
2019-03-12 19:32 ` Sergio Durigan Junior
2019-03-12 19:39 ` Elijah Newren
2019-03-12 19:58 ` Sergio Durigan Junior
2019-03-13 20:40 ` Phillip Wood
2019-03-13 20:48 ` Sergio Durigan Junior
2019-03-13 20:59 ` Jeff King
2019-03-13 21:07 ` Sergio Durigan Junior [this message]
2022-10-28 16:04 ` Possible race condition with git-rebase + .git/index.lock - probably a gettext issue Mingun
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lg1i4h6g.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).