From: Tay Ray Chuan <rctay89@gmail.com>
Date: Sun, 07 Jun 2009 00:45:50 GMT
Subject: Re: [PATCH 00/23] http*: refactor (v6)
Message-ID: <be6fef0d0906061745q1cd65958raff19241b221e447@mail.gmail.com>
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