From: Tay Ray Chuan <rctay89@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Mike Hommey <mh@glandium.org>
Subject: Re: [PATCH 00/23] http*: refactor (v6)
Date: Sun, 7 Jun 2009 08:45:50 +0800 [thread overview]
Message-ID: <be6fef0d0906061745q1cd65958raff19241b221e447@mail.gmail.com> (raw)
In-Reply-To: <m3tz2t43xr.fsf@localhost.localdomain>
Hi,
On Sun, Jun 7, 2009 at 2:23 AM, Jakub Narebski<jnareb@gmail.com> wrote:
> Before git-send-email learned --cover option, I have used the
> following commands to generate "Table of contents" for a patch series:
> * generate patches to some subdirectory using '-o' option
> of git-format-patch
> * grep for subject and remove "Subject:" line:
> $ grep -h "Subject:" mdir/* | sed -e 's/Subject://' >> mdir/0000-cover.txt
>
> This way I had list of patches in the series in actual order...
I see. I output my patches into one big mbox file; I'm sure your
technique can be tailored to that.
But then, isn't there a way to do this with git-format-patch or git-something?
> P.S. Tay Ray Chuan, this patch series is again not being replies to
> cover letter...
Sorry about that; I already used --thread (you can see that the
patches all have In-Reply-To headers), but the Message-Id of the cover
letter changed while I sent it out, so I messed up.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2009-06-07 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 8:42 [PATCH 00/23] http*: refactor (v6) Tay Ray Chuan
2009-06-06 18:04 ` Junio C Hamano
2009-06-06 18:23 ` Jakub Narebski
2009-06-07 0:45 ` Tay Ray Chuan [this message]
2009-06-07 0:41 ` Tay Ray Chuan
2009-06-10 10:36 ` Tay Ray Chuan
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=be6fef0d0906061745q1cd65958raff19241b221e447@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=mh@glandium.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).