git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Make the 'lock file' exists error more informative

From
John Tapsell <johnflux@gmail.com>
Date
Mar 4, 2009, 15:03 UTC
Message-ID
<43d8ce650903040703v2a743797rc30724f8c1c608e7@mail.gmail.com>
In-Reply-To
<1236178844-7958-1-git-send-email-johnflux@gmail.com>
Argh, I'm so sorry.  After all that, I went and sent a broken version.
 Plus I just noticed another bug.  Will retry..
2009/3/4 John Tapsell <johnflux@gmail.com>:
Show 23 quoted lines
> It looks like someone did 90% of the work, then forgot to actually use
> the function
> ---
>  lockfile.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lockfile.c b/lockfile.c
> index 1db1a2f..6772f38 100644
> --- a/lockfile.c
> +++ b/lockfile.c
> @@ -184,7 +184,7 @@ int hold_lock_file_for_append(struct lock_file *lk, const char *path, int flags)
>        fd = lock_file(lk, path, flags);
>        if (fd < 0) {
>                if (flags & LOCK_DIE_ON_ERROR)
> -                       die("unable to create '%s.lock': %s", path, strerror(errno));
> +                       unable_to_lock_index_die(path, strerror(errno));
>                return fd;
>        }
>
> --
> 1.6.2.rc1.3.g7d31b.dirty
>
>
Previous: John Tapsell
Message 2 of 2 in “Make the 'lock file' exists error more informative”
  1. Make the 'lock file' exists error more informativeJohn Tapsell, Mar 4, 2009
  2. John TapsellMar 4, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.