From: Andreas Ericsson <ae@op5.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: shortlog, was Re: merge-recursive, was Re: What's in git.git
Date: Thu, 26 Oct 2006 13:35:21 +0200 [thread overview]
Message-ID: <45409D79.8010909@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.63.0610261114520.3286@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
>
> BTW what happened to the builtin shortlog? It is the last Perl script I
> use regularly... (should make people happy who are stuck with Activision
> Perl...)
>
I keep writing
git log --short
when I really want
git log --pretty=short | git shortlog
I'll have a look at making it work if I get a spare moment.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
next prev parent reply other threads:[~2006-10-26 11:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 8:47 What's in git.git Junio C Hamano
2006-10-26 9:12 ` Jakub Narebski
2006-10-26 9:24 ` Junio C Hamano
2006-10-26 12:08 ` Petr Baudis
2006-10-26 12:17 ` Jakub Narebski
2006-10-26 9:18 ` merge-recursive, was " Johannes Schindelin
2006-10-26 9:25 ` Jakub Narebski
2006-10-26 9:35 ` Junio C Hamano
2006-10-26 9:47 ` Jakub Narebski
2006-10-26 13:23 ` Nicolas Pitre
2006-10-26 12:34 ` git-shortlog mailmap Petr Baudis
2006-10-26 12:41 ` Jakub Narebski
2006-10-26 12:43 ` Andreas Ericsson
2006-10-26 13:13 ` Jakub Narebski
2006-10-26 13:16 ` Johannes Schindelin
2006-10-26 13:29 ` Petr Baudis
2006-10-26 9:26 ` merge-recursive, was Re: What's in git.git Junio C Hamano
2006-10-26 10:00 ` Junio C Hamano
2006-10-26 10:56 ` Johannes Schindelin
2006-10-26 11:35 ` Andreas Ericsson [this message]
2006-10-26 13:39 ` shortlog, was " Nicolas Pitre
2006-10-26 13:45 ` Andreas Ericsson
2006-10-26 9:19 ` Jakub Narebski
2006-10-27 1:10 ` Petr Baudis
2006-10-26 12:22 ` Petr Baudis
2006-10-26 17:27 ` Andy Whitcroft
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=45409D79.8010909@op5.se \
--to=ae@op5.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.