Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: [REGRESSION] Interrupted clone/fetch leaves .lock files around
Date: Tue, 06 Jun 2006 12:09:44 -0700	[thread overview]
Message-ID: <7vmzcqp0cn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060606185148.GA15521@diku.dk> (Jonas Fonseca's message of "Tue, 6 Jun 2006 20:51:48 +0200")

Jonas Fonseca <fonseca@diku.dk> writes:

> 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.

  parent reply	other threads:[~2006-06-06 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 18:51 [REGRESSION] Interrupted clone/fetch leaves .lock files around Jonas Fonseca
2006-06-06 19:02 ` Jonas Fonseca
2006-06-06 19:09 ` Junio C Hamano [this message]
2006-06-06 21:58   ` Junio C Hamano

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=7vmzcqp0cn.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=fonseca@diku.dk \
    --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