From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
David Steven Tweed <d.s.tweed@reading.ac.uk>,
git@vger.kernel.org
Subject: Re: [PATCH] prune: heed --expire for stale packs, add a test
Date: Wed, 06 Feb 2008 09:12:38 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802060910340.2732@xanadu.home> (raw)
In-Reply-To: <7v7ihi64xm.fsf@gitster.siamese.dyndns.org>
On Tue, 5 Feb 2008, Junio C Hamano wrote:
> They are not "stale packs", but temporary files that wanted to
> become pack but did not succeed. Perhaps "stale temporary
> packs"?
>
> Shouldn't we do something similar to objects/pack/pack-*.temp
> files and objects/??/*.temp that http walker leaves?
Instead, I think http walker should be made to use the same location and
filename pattern for its temporary files as the rest of the code.
Nicolas
next prev parent reply other threads:[~2008-02-06 14:13 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 [this message]
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
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=alpine.LFD.1.00.0802060910340.2732@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=d.s.tweed@reading.ac.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).