From: Steven Grimm <koreth@midwinter•com>
To: Len Brown <lenb@kernel•org>
Cc: git@vger•kernel.org
Subject: [PATCH] Print a more accurate error message when we fail to create a lock file.
Date: Fri, 5 Jan 2007 19:14:04 -0800 [thread overview]
Message-ID: <20070106031404.GA4863@midwinter.com> (raw)
Signed-off-by: Steven Grimm <koreth@midwinter•com>
---
lockfile.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lockfile.c b/lockfile.c
index 731bbf3..4824f4d 100644
--- a/lockfile.c
+++ b/lockfile.c
@@ -49,7 +49,7 @@ int hold_lock_file_for_update(struct lock_file *lk,
const char *path, int die_on
{
int fd = lock_file(lk, path);
if (fd < 0 && die_on_error)
- die("unable to create '%s': %s", path, strerror(errno));
+ die("unable to create '%s.lock': %s", path, strerror(errno));
return fd;
}
--
1.5.0.rc0.g244a7
reply other threads:[~2007-01-06 3:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070106031404.GA4863@midwinter.com \
--to=koreth@midwinter$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=lenb@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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