From: Junio C Hamano <gitster@pobox•com>
To: Daniel Barkalow <barkalow@iabervon•org>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 00/11] Build in clone
Date: Sat, 08 Mar 2008 21:32:46 -0800 [thread overview]
Message-ID: <7v4pbgsbr5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0803081803250.19665@iabervon.org> (Daniel Barkalow's message of "Sat, 8 Mar 2008 18:03:52 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon•org> writes:
> (Unrelated note: it might actually be good to use some sort of log
> instead of shortlog in --cover-letter, at least as an option, in order
> to list the contents of the series with the patch numbers and order
> they have)
Certainly, I think that is a good idea.
prev parent reply other threads:[~2008-03-09 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 23:03 [PATCH 00/11] Build in clone Daniel Barkalow
2008-03-08 23:15 ` Johannes Schindelin
2008-03-08 23:20 ` Daniel Barkalow
2008-03-09 5:32 ` Junio C Hamano [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=7v4pbgsbr5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=barkalow@iabervon$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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