From: Nicolas Pitre <nico@cam.org>
To: Andreas Ericsson <ae@op5.se>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: shortlog, was Re: merge-recursive, was Re: What's in git.git
Date: Thu, 26 Oct 2006 09:39:19 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610260937070.12418@xanadu.home> (raw)
In-Reply-To: <45409D79.8010909@op5.se>
On Thu, 26 Oct 2006, Andreas Ericsson wrote:
> 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.
Why don't you simply drop the --pretty=short altogether?
git log | git shortlog
next prev parent reply other threads:[~2006-10-26 13:39 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 ` shortlog, was " Andreas Ericsson
2006-10-26 13:39 ` Nicolas Pitre [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0610260937070.12418@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).