From: "David Tweed" <david.tweed@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "David Steven Tweed" <d.s.tweed@reading.ac.uk>,
git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: [PATCH] Make git prune remove temporary packs that look like write failures
Date: Wed, 6 Feb 2008 20:25:01 +0000 [thread overview]
Message-ID: <e1dab3980802061225l21cc35b5u288695924f56f3ca@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802061511440.2732@xanadu.home>
On Feb 6, 2008 8:16 PM, Nicolas Pitre <nico@cam.org> wrote:
> On Wed, 6 Feb 2008, David Tweed wrote:
> > Ah, I hadn't realised this was an intended usage of --expire. Since as
> > you note there's no way to tell an abandoned tmp pack from one that's
> > in the process of being written, following expire is probably
> > necessary for safety. I'll look at adding support for that.
>
> Did you miss Johannes ' patch? He posted it yesterday and you were even
> CC'd. It did exactly that on top of yours already.
I had missed it (I've only just started reading email). Thanks for
pointing it out.
--
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"while having code so boring anyone can maintain it, use Python." --
attempted insult seen on slashdot
next prev parent reply other threads:[~2008-02-06 20:25 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 [this message]
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=e1dab3980802061225l21cc35b5u288695924f56f3ca@mail.gmail.com \
--to=david.tweed@gmail.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).