From: Junio C Hamano <gitster@pobox.com>
To: David Steven Tweed <d.s.tweed@reading.ac.uk>
Cc: git@vger.kernel.org, nico@cam.org, Johannes.Schindelin@gmx.de
Subject: Re: [PATCH] Make git prune remove temporary packs that look like write failures
Date: Wed, 06 Feb 2008 02:02:20 -0800 [thread overview]
Message-ID: <7vve52z9lf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.GSO.4.63.0802051844220.15867@suma3> (David Steven Tweed's message of "Tue, 5 Feb 2008 18:49:31 +0000 (GMT)")
David Steven Tweed <d.s.tweed@reading.ac.uk> writes:
> Write errors when repacking (eg, due to out-of-space conditions)
> can leave temporary packs (and possibly other files beginning
> with "tmp_") lying around which no existing
> codepath removes and which aren't obvious to the casual user.
> These can also be multi-megabyte files wasting noticeable space.
> Unfortunately there's no way to definitely tell in builtin-prune
> that a tmp_ file is not being used by a concurrent process.
> However, it is documented that pruning should only be done
> on a quiet repository. The names of removed files are printed.
>
> Signed-off-by: David Tweed (david.tweed@gmail.com)
> ---
>
> Per discussion of previous version, this now unconditionally
> removes any tmp_ file existing when prune is run.
Sorry, can't apply
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
prev parent reply other threads:[~2008-02-06 10:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 18:49 [PATCH] Make git prune remove temporary packs that look like write failures David Steven Tweed
2008-02-05 19:02 ` Nicolas Pitre
2008-02-05 20:06 ` [PATCH] prune: heed --expire for stale packs, add a test Johannes Schindelin
2008-02-05 20:13 ` Nicolas Pitre
2008-02-06 5:15 ` Junio C Hamano
2008-02-06 7:41 ` Johannes Schindelin
2008-02-06 14:12 ` Nicolas Pitre
2008-02-06 20:30 ` Junio C Hamano
2008-02-06 16:48 ` [PATCH] Make git prune remove temporary packs that look like write failures Brandon Casey
2008-02-06 18:59 ` David Tweed
2008-02-06 19:41 ` Brandon Casey
2008-02-06 19:57 ` David Tweed
2008-02-06 20:07 ` Nicolas Pitre
2008-02-06 20:43 ` Brandon Casey
2008-02-06 19:10 ` David Tweed
2008-02-06 19:31 ` Nicolas Pitre
2008-02-06 20:02 ` David Tweed
2008-02-06 20:16 ` Nicolas Pitre
2008-02-06 20:25 ` David Tweed
2008-02-06 10:02 ` Junio C Hamano [this message]
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=7vve52z9lf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=d.s.tweed@reading.ac.uk \
--cc=git@vger.kernel.org \
--cc=nico@cam.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;
as well as URLs for NNTP newsgroup(s).