From a8c37a0e011d67e3192834a0fffe17452ea57a08 Mon Sep 17 00:00:00 2001 From: Matthieu Moy Date: Thu, 7 Jan 2010 15:54:10 +0100 Subject: [PATCH] lockfile: show absolute filename in unable_to_lock_message When calling a git command from a subdirectory and a file locking fails, the user will get a path relative to the root of the worktree, which is invalid from the place where the command is ran. Make it easy for the user to know which file it is. Signed-off-by: Matthieu Moy Signed-off-by: Junio C Hamano --- lockfile.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/lockfile.c b/lockfile.c index 6851fa55a..b0d74cddd 100644 --- a/lockfile.c +++ b/lockfile.c @@ -164,9 +164,10 @@ static char *unable_to_lock_message(const char *path, int err) "If no other git process is currently running, this probably means a\n" "git process crashed in this repository earlier. Make sure no other git\n" "process is running and remove the file manually to continue.", - path, strerror(err)); + make_nonrelative_path(path), strerror(err)); } else - strbuf_addf(&buf, "Unable to create '%s.lock': %s", path, strerror(err)); + strbuf_addf(&buf, "Unable to create '%s.lock': %s", + make_nonrelative_path(path), strerror(err)); return strbuf_detach(&buf, NULL); } -- 2.30.2