From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: David Steven Tweed <d.s.tweed@reading.ac.uk>
Cc: git@vger.kernel.org, nico@cam.org, casey@nrlssc.navy.mil
Subject: Re: [PATCH v2] Make git prune remove temporary packs that look like write failures
Date: Thu, 7 Feb 2008 01:25:20 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0802070123480.8543@racer.site> (raw)
In-Reply-To: <Pine.GSO.4.63.0802062342020.7187@suma3>
Hi,
On Wed, 6 Feb 2008, David Steven Tweed wrote:
> This version incorporates all the agreed with changes from the previous
> version, and since I was modifying the relevant context lines it
> includes Johannes' code honouring --expire (but not the test he wrote
> which is presumably best sent as a separate patch from him).
No, I don't want the tests as a separate patch. They are intrinsic to
your patch, since they show that your patch does what it's supposed to do
(at least in an empirical way).
Ciao,
Dscho
prev parent reply other threads:[~2008-02-07 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:48 [PATCH v2] Make git prune remove temporary packs that look like write failures David Steven Tweed
2008-02-07 1:25 ` Johannes Schindelin [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=alpine.LSU.1.00.0802070123480.8543@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=casey@nrlssc.navy.mil \
--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