From: Nate Parsons <parsons.nate@gmail.com>
To: kusmabite@gmail.com
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
git@vger.kernel.org
Subject: Re: git .lock file error
Date: Thu, 30 Sep 2010 20:57:20 -0400 [thread overview]
Message-ID: <AANLkTi=eMt_OduJ8d=5mhhnt+q-Mpb8b1iimt_0bws3f@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikV=f1ncAxQ1LWzntnOwiBKMfw_D8Mcuh+wCO3+@mail.gmail.com>
On Thu, Sep 30, 2010 at 7:45 PM, Erik Faye-Lund <kusmabite@gmail.com> wrote:
> Are you running some anti-virus, or from a Dropbox-folder (or
> something similar)? If so, these applications tend to open files for a
> short while and then release the file handle. This can some times
> cause race conditions with other software, like Git.
>
> I haven't looked into this particular code-path for what kind of
> hazards might be, but this sounds very much like one such case to me.
>
Any of these things are possible. As much as I'd like to find the root
cause of this problem, isn't making Git more robust a good thing in
general? Finding every program that could conflict with Git and
disabling/uninstalling it isn't really a good long term solution, I
think.
next prev parent reply other threads:[~2010-10-01 0:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 15:19 git .lock file error Nate Parsons
2010-09-20 2:42 ` Nate Parsons
2010-09-30 18:00 ` Nate Parsons
2010-09-30 19:13 ` Ævar Arnfjörð Bjarmason
2010-09-30 20:15 ` Junio C Hamano
2010-09-30 21:10 ` Nate Parsons
2010-09-30 21:16 ` Ævar Arnfjörð Bjarmason
2010-09-30 23:45 ` Erik Faye-Lund
2010-10-01 0:57 ` Nate Parsons [this message]
[not found] ` <AANLkTik2HtyVGz6xFb_VmCh1gSAA_vwpUXhytHFzgCwa@mail.gmail.com>
2010-10-01 1:59 ` Erik Faye-Lund
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='AANLkTi=eMt_OduJ8d=5mhhnt+q-Mpb8b1iimt_0bws3f@mail.gmail.com' \
--to=parsons.nate@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@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 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).