From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Joe Perches <joe@perches.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] builtin-log: Add options to --coverletter
Date: Sat, 16 May 2009 01:07:19 -0400 [thread overview]
Message-ID: <20090516050718.GA7330@sigio.peff.net> (raw)
In-Reply-To: <7v63g2tewu.fsf@alter.siamese.dyndns.org>
On Fri, May 15, 2009 at 11:11:13AM -0700, Junio C Hamano wrote:
> This is a tangent, but I do not think the current cover-letter that uses
> shortlog matches everybody's needs. The shortlog format lists commits
> grouped by the author and does not number them, and it makes it hard to
> match which message in the series corresponds to which entry in the cover
> letter, especially when your series have a resend of somebody else's patch
> in it. I wouldn't be surprised if somebody comes up with a different
> style that is based on "git log --reverse --oneline A..B" output (perhaps
> without the shortened object name part) and name it the "oneline" style,
> e.g.
>
> From: Jeff King
>
> *** BLURB HERE ***
> The following patches do ...
>
> 1/2 parseopt: add OPT_NEGBIT (Réne Scharfe)
> 2/2 ls-files: make --no-empty-directory negatable
At one point I was working on --pretty=format specifiers for "total
number of commits" and "incremental commit number". The eventual goal
being an option like coverletter.logformat that you could set to
"%xi/%xn %s".
Sadly, the code got a bit messy because the feature straddles the line
of pretty.c and actual rev traversal. I started some refactoring, but
dropped it halfway through, and now of course it is woefully out of date
(a lesson in "merge early, merge often"). So I just pipe "git log
--oneline" through nl manually. ;)
So yes, I think somebody would be interested in alternate styles. And
while I think most people would want to set their default style as a
config variable, it may make sense to override on the command-line
(e.g., for a series that is mostly from you versus one that is from
mixed authors).
-Peff
next prev parent reply other threads:[~2009-05-16 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 0:57 [RFC PATCH] builtin-log: Add options to --coverletter Joe Perches
2009-05-15 18:11 ` Junio C Hamano
2009-05-15 20:19 ` Joe Perches
2009-05-15 21:51 ` Junio C Hamano
2009-05-15 22:07 ` Joe Perches
2009-05-16 2:30 ` Junio C Hamano
2009-05-16 0:46 ` Joe Perches
2009-05-16 2:32 ` Junio C Hamano
2009-05-16 5:07 ` Jeff King [this message]
2009-05-16 17:35 ` James Cloos
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=20090516050718.GA7330@sigio.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joe@perches.com \
/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).