From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org
Subject: Re: author/commit counts
Date: Sat, 23 Dec 2006 14:28:00 +0000 (UTC) [thread overview]
Message-ID: <loom.20061223T152605-994@post.gmane.org> (raw)
In-Reply-To: 20061223023719.GA8734@spearce.org
Shawn Pearce <spearce <at> spearce.org> writes:
> $ git log | grep ^Author | cut -d\< -f1 | sort \
> | uniq -c | sort -n -r | head -20
As Junio pointed out in another mail, "git shortlog -n -s | head -20" is
shorter...
> You can also see the very clear gap between Junio and the rest of the
> world. There's very little dispute about who really codes Git.
Note that this still holds when doing the technically correct thing:
$ git shortlog -n -s --no-merges
Ciao,
Dscho
next prev parent reply other threads:[~2006-12-23 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-23 2:10 author/commit counts Randy Dunlap
2006-12-23 2:37 ` Shawn Pearce
2006-12-23 4:44 ` Linus Torvalds
2006-12-23 14:28 ` Johannes Schindelin [this message]
2006-12-23 4:37 ` Randal L. Schwartz
2006-12-23 5:27 ` Randy Dunlap
2006-12-23 4:43 ` Junio C Hamano
2006-12-23 5:24 ` Randy Dunlap
2006-12-23 5:29 ` Shawn Pearce
2006-12-23 5:06 ` Nicolas Pitre
2006-12-23 14:22 ` Johannes Schindelin
2006-12-23 14:31 ` Nicolas Pitre
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=loom.20061223T152605-994@post.gmane.org \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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