From: Nicolas Pitre <nico@cam.org>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Ingo Molnar <mingo@elte.hu>, Jeff King <peff@peff.net>,
Jakub Narebski <jnareb@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Invert numbers and names in the git-shortlog summary mode.
Date: Tue, 11 Dec 2007 10:34:01 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.99999.0712111032530.555@xanadu.home> (raw)
In-Reply-To: <20071211152412.GB15448@artemis.madism.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2011 bytes --]
On Tue, 11 Dec 2007, Pierre Habouzit wrote:
> On Tue, Dec 11, 2007 at 02:57:09PM +0000, Ingo Molnar wrote:
> >
> > * Pierre Habouzit <madcoder@debian.org> wrote:
> >
> > > Agreed, here is the patch that does that, and a sample output is:
> > >
> > > $ git shortlog -n -s -e HEAD -- builtin-commit.c
> > > 11 Junio C Hamano <gitster@pobox.com>
> > > 6 Johannes Schindelin <Johannes.Schindelin@gmx.de>
> > > 6 Kristian Høgsberg <krh@redhat.com>
> > > 2 Jeff King <peff@peff.net>
> > > 1 Alex Riesen <raa.lkml@gmail.com>
> > > 1 Pierre Habouzit <madcoder@debian.org>
> > > 1 Shawn Bohrer <shawn.bohrer@gmail.com>
> > > 1 Wincent Colaiuta <win@wincent.com>
> >
> > great - this looks really neat!
> >
> > btw., stupid question: why are the git-shortlog command line arguments
> > different from git-log? I got used to things like:
> >
> > git-log kernel/
> >
> > so for me it would be natural to just do:
> >
> > git-shortlog -n -s kernel/
> >
> > but this currently produces this output:
> >
> > $ git-shortlog -n -s kernel/
> > (reading log to summarize from standard input)
> >
> > which is quite a bit confusing to someone who'd like to keep as few
> > details of command line arguments in his head as possible :-)
>
> Because git-shortlog insists on you passing a reference first, HEAD is
> not implicit if you pass something that looks like a path first. This is
> arguably wrong. What you meant here is:
>
> $ git-shortlog -n -s HEAD kernel/
>
> The reason IIRC is that git-shortlog once only read things on stdin, and
> this keeps backward compatbility to `git-shortlog` without any
> arguments.
>
> Sometimes history hurts :) I don't think there is much we can do on a
> short timescale. Maybe the old way can be slowly deprecated, and then
> git-shortlog will be able to act like git-log.
At least, HEAD could be assumed by default when stdin is a tty.
Nicolas
next prev parent reply other threads:[~2007-12-11 15:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 9:34 git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
2007-12-07 9:58 ` Junio C Hamano
2007-12-07 10:25 ` Junio C Hamano
2007-12-07 11:21 ` Ingo Molnar
2007-12-07 19:28 ` Junio C Hamano
2007-12-07 19:46 ` Ingo Molnar
2007-12-07 21:34 ` Jeff King
2007-12-07 21:35 ` Jeff King
2007-12-07 21:44 ` Junio C Hamano
2007-12-07 21:55 ` Jeff King
2007-12-07 22:03 ` Junio C Hamano
2007-12-07 22:07 ` Jeff King
2007-12-08 2:54 ` Junio C Hamano
2007-12-08 5:36 ` Christian Couder
2007-12-08 15:29 ` Ingo Molnar
2007-12-09 5:33 ` git-bisect run make -j64 kernel/ (was Re: git-bisect feature suggestion: "git-bisect diff") Christian Couder
2007-12-12 9:43 ` Ingo Molnar
2007-12-11 9:24 ` git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
2007-12-11 9:29 ` Pierre Habouzit
2007-12-11 10:13 ` Jakub Narebski
2007-12-11 11:59 ` Pierre Habouzit
2007-12-11 12:25 ` Jeff King
2007-12-11 12:33 ` Jeff King
2007-12-11 14:05 ` Ingo Molnar
2007-12-11 14:43 ` [PATCH] Invert numbers and names in the git-shortlog summary mode Pierre Habouzit
2007-12-11 14:57 ` Ingo Molnar
2007-12-11 15:24 ` Pierre Habouzit
2007-12-11 15:34 ` Nicolas Pitre [this message]
2007-12-11 18:09 ` Junio C Hamano
2007-12-11 15:48 ` Ingo Molnar
2007-12-11 16:07 ` Pierre Habouzit
2007-12-11 16:11 ` Pierre Habouzit
2007-12-11 21:13 ` Ingo Molnar
2007-12-11 22:21 ` Junio C Hamano
2007-12-11 17:58 ` Junio C Hamano
2007-12-11 10:17 ` git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
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=alpine.LFD.0.99999.0712111032530.555@xanadu.home \
--to=nico@cam.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=madcoder@debian.org \
--cc=mingo@elte.hu \
--cc=peff@peff.net \
/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).