git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] More friendly message when locking the index fails.
Date: Wed, 4 Feb 2009 12:50:06 +0100	[thread overview]
Message-ID: <bd6139dc0902040350n3af5d37ctc6976fd77671fb82@mail.gmail.com> (raw)
In-Reply-To: <1233741505-24020-1-git-send-email-Matthieu.Moy@imag.fr>

On Wed, Feb 4, 2009 at 10:58, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> +                                   "This probably means a git process crashed in this repository earlier.\n"
> +                                   "Make sure no other git process is running and remove the file manually.",
> +                                   get_index_file(), strerror(lock_error));

How about "If no other git process is currently running, this probably
means...." instead? E.g., sometimes I run 'git commit' in one terminal
window, and then switch to another before committing (to review the
diff for example), which would cause an index.lock file to be present
validly.

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2009-02-04 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04  8:36 Recovering the index after a git crash? Matthieu Moy
2009-02-04  9:58 ` [PATCH/RFC] More friendly message when locking the index fails Matthieu Moy
2009-02-04 11:50   ` Sverre Rabbelier [this message]
2009-02-06 13:38 ` Recovering the index after a git crash? Mikael Magnusson
2009-02-06 14:36 ` [PATCH] More friendly message when locking the index fails Matthieu Moy
2009-02-06 15:09   ` [PATCH v3] " Matthieu Moy
2009-02-07  0:37     ` Junio C Hamano
2009-02-19 12:54       ` [PATCH] " Matthieu Moy
2009-02-19 14:12         ` Sverre Rabbelier

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=bd6139dc0902040350n3af5d37ctc6976fd77671fb82@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=Matthieu.Moy@imag.fr \
    --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).