From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Git Mailing List <git@vger.kernel.org>
Subject: 'shortlog' script for git
Date: Sat, 04 Jun 2005 01:49:37 -0400 [thread overview]
Message-ID: <42A140F1.5070707@pobox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
I've been wanting a shortlog script for summarizing my kernel
submissions to Linus for a while. This is now written, and the results
are attached. Simply use like
git-shortlog < changes.txt
or
git-shortlog changes.txt
The changeset format the Perl script parses is that of
http://www.kernel.org/pub/linux/kernel/people/jgarzik/git-changes-script
I'll change it to parse the git-whatchanged output format sometime soon;
Linus hates it when I use git-changes-script since he thinks its ugly :)
Jeff
[-- Attachment #2: git-shortlog --]
[-- Type: text/plain, Size: 1263 bytes --]
#!/usr/bin/perl -w
use strict;
my ($author, $desc, %map);
my $pstate = 1;
while (<>) {
# skip to '^commit '
if ($pstate == 1) {
next unless /^commit /;
$pstate++;
}
# get author
elsif ($pstate == 2) {
next unless /^author (.*) \S+ \S+ \S+ \S+ \S+ \S+\s*$/;
$author = $1;
$pstate++;
}
# skip to blank line
elsif ($pstate == 3) {
next unless /^\s*$/;
$pstate++;
}
# skip to non-blank line
elsif ($pstate == 4) {
next if /^\s*$/;
chomp;
$desc = $_;
&shortlog_entry($author, $desc);
$pstate = 1;
}
else {
die "invalid parse state $pstate";
}
}
&shortlog_output;
exit(0);
sub shortlog_entry($$) {
my ($tmp_author, $tmp_desc) = @_;
my ($obj);
$tmp_desc =~ s#/pub/scm/linux/kernel/git/#/.../#g;
$tmp_desc =~ s/^\[PATCH] //g;
$tmp_desc =~ s/^\s+//g;
if (exists $map{$tmp_author}) {
# grab ref
$obj = $map{$tmp_author};
# add desc to array
push(@$obj, $tmp_desc);
} else {
# create ref to new array
my @arr = ($tmp_desc);
$obj = \@arr;
# store new entry in author map
$map{$tmp_author} = $obj;
}
}
sub shortlog_output {
my ($obj);
foreach $author (sort keys %map) {
print "$author:\n";
$obj = $map{$author};
foreach $desc (@$obj) {
print " $desc\n";
}
print "\n";
}
}
reply other threads:[~2005-06-04 5:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42A140F1.5070707@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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 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.