From: Jakub Narebski Date: Sat, 06 Jun 2009 18:23:17 GMT Subject: Re: [PATCH 00/23] http*: refactor (v6) Message-ID: In-Reply-To: <7v8wk5dyrw.fsf@alter.siamese.dyndns.org> Junio C Hamano writes: > Tay Ray Chuan writes: [...] > By the way, this is not your fault at all, but for a patch series > description, "shortlog" is a sucky way, as we can see below. When you > talk about "patch #15", the reader cannot find which one you are talking > about but has to go back to the MUA, so the list is useless for that > purpose. > > The output of "shortlog" in an e-mail message is wonderful when you are a > subsystem maintainer who bundles many people's work and are sending out a > pull request (i.e. you are transferring the whole graph in "take it or > reject all" fashion, and you can refer to an individual changeset with its > commit object name). > > But I think a cover letter to a patch series should serve as an easy index > from patch number to the title in some way, and "shortlog" is not suitable > for that eapecially for a multi-author series. 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... P.S. Tay Ray Chuan, this patch series is again not being replies to cover letter... -- Jakub Narebski Poland ShadeHawk on #git