From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jari Aalto" <jari.aalto@cante.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Lukas Sandström" <lukass@etek.chalmers.se>
Subject: Re: [PATCH] In Examples, explain option -r and refer to git-rev-list[1]
Date: Mon, 27 Aug 2007 06:02:44 -0400 [thread overview]
Message-ID: <20070827100244.GA23248@coredump.intra.peff.net> (raw)
In-Reply-To: <7vy7fxjo90.fsf@gitster.siamese.dyndns.org>
On Mon, Aug 27, 2007 at 02:55:07AM -0700, Junio C Hamano wrote:
> > But yes, this is post-1.5.3, so I will shut up rather than nitpicking
> > your "not meant to be applied now" patches.
>
> Thanks for your comments; rather than shutting up, could you
> send an improvement after 1.5.3 happens?
Will do.
-Peff
prev parent reply other threads:[~2007-08-27 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 15:40 [PATCH] In Examples, explain option -r and refer to git-rev-list[1] Jari Aalto
2007-08-27 8:02 ` Lukas Sandström
2007-08-27 8:14 ` Junio C Hamano
2007-08-27 8:33 ` Junio C Hamano
2007-08-27 8:44 ` Jeff King
2007-08-27 9:55 ` Junio C Hamano
2007-08-27 10:02 ` 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=20070827100244.GA23248@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jari.aalto@cante.net \
--cc=lukass@etek.chalmers.se \
/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).