From: Jeff King <peff@peff.net>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/3] fix a few issues before v1.5.0
Date: Thu, 1 Feb 2007 12:44:02 -0500 [thread overview]
Message-ID: <20070201174402.GA26902@coredump.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0702011226570.3021@xanadu.home>
On Thu, Feb 01, 2007 at 12:29:00PM -0500, Nicolas Pitre wrote:
> After those patches I'm happy to let it go loose.
I think this addresses my concerns with the message; thanks.
-Peff
prev parent reply other threads:[~2007-02-01 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 17:29 [PATCH 0/3] fix a few issues before v1.5.0 Nicolas Pitre
2007-02-01 17:44 ` Jeff King [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=20070201174402.GA26902@coredump.intra.peff.net \
--to=peff@peff.net \
--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).