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

Re: [REGRESSION] Interrupted clone/fetch leaves .lock files around

From
Junio C Hamano <junkio@cox.net>
Date
Jun 6, 2006, 19:09 UTC
Message-ID
<7vmzcqp0cn.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060606185148.GA15521@diku.dk>
Jonas Fonseca <fonseca@diku.dk> writes:
Show 10 quoted lines
> Below is my feeble attempt at a (tested) fix.
>
> diff --git a/fetch.c b/fetch.c
> index e040ef9..861dc60 100644
> --- a/fetch.c
> +++ b/fetch.c
> @@ -1,3 +1,5 @@
> +#include <signal.h>
> +
>  #include "fetch.h"

I suspect you could do something similar to what we already do for index updates using atexit(). Let me take a look.

Previous: Jonas FonsecaNext: Junio C Hamano
Message 3 of 4 in “[REGRESSION] Interrupted clone/fetch leaves .lock files around”
  1. Jonas FonsecaJun 6, 2006
  2. Jonas FonsecaJun 6, 2006
  3. Junio C HamanoJun 6, 2006
  4. Junio C HamanoJun 6, 2006

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.