From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: git@vger.kernel.org
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: [PATCH/RFC] More friendly message when locking the index fails.
Date: Wed, 4 Feb 2009 10:58:25 +0100 [thread overview]
Message-ID: <1233741505-24020-1-git-send-email-Matthieu.Moy@imag.fr> (raw)
In-Reply-To: <vpqljsma99t.fsf@bauges.imag.fr>
Just saying that index.lock exists doesn't tell the user _what_ to do
to fix the problem. We should give an indication that it's normally
safe to delete index.lock after making sure git isn't running here.
---
> I'll write a FAQ entry on the wiki with answers, and that would
> probably be a good idea to give indication to the user directly in the
> error message too, otherwise, the problem can be blocking for
> beginners.
Something along the lines of this patch maybe?
builtin-update-index.c | 11 +++++++++--
lockfile.c | 9 ++++++++-
2 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/builtin-update-index.c b/builtin-update-index.c
index 5604977..ab8ab8f 100644
--- a/builtin-update-index.c
+++ b/builtin-update-index.c
@@ -742,8 +742,15 @@ int cmd_update_index(int argc, const char **argv, const char *prefix)
if (newfd < 0) {
if (refresh_flags & REFRESH_QUIET)
exit(128);
- die("unable to create '%s.lock': %s",
- get_index_file(), strerror(lock_error));
+ if (lock_error == EEXIST) {
+ die("Unable to create '%s.lock': %s\n"
+ "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));
+ } else {
+ die("Unable to create '%s.lock': %s",
+ get_index_file(), strerror(lock_error));
+ }
}
if (write_cache(newfd, active_cache, active_nr) ||
commit_locked_index(lock_file))
diff --git a/lockfile.c b/lockfile.c
index 021c337..bb59f7e 100644
--- a/lockfile.c
+++ b/lockfile.c
@@ -159,7 +159,14 @@ int hold_lock_file_for_update(struct lock_file *lk, const char *path, int flags)
{
int fd = lock_file(lk, path, flags);
if (fd < 0 && (flags & LOCK_DIE_ON_ERROR))
- die("unable to create '%s.lock': %s", path, strerror(errno));
+ if (errno == EEXIST) {
+ die("Unable to create '%s.lock': %s\n"
+ "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.",
+ path, strerror(errno));
+ } else {
+ die("Unable to create '%s.lock': %s", path, strerror(errno));
+ }
return fd;
}
--
1.6.1.2.322.g01114.dirty
next prev parent reply other threads:[~2009-02-04 10:06 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 ` Matthieu Moy [this message]
2009-02-04 11:50 ` [PATCH/RFC] More friendly message when locking the index fails Sverre Rabbelier
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=1233741505-24020-1-git-send-email-Matthieu.Moy@imag.fr \
--to=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).