From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Cleaning up log messages
Date: Sun, 27 Jul 2008 20:01:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807272000270.5526@eeepc-johanness> (raw)
In-Reply-To: <9e4733910807271050y7fb5f77coec05bd68421baaab@mail.gmail.com>
Hi,
On Sun, 27 Jul 2008, Jon Smirl wrote:
> I was playing around with git log for the kernel and observed that there
> is a lot of noise when trying to do statistics on the number of commits.
>
> For example:
>
> Author: Greg K-H <gregkh@suse.de>
> Author: Greg KH <gregkh@suse.de>
> Author: Greg KH <greg@kroah.com>
> Author: Greg KH <greg@press.(none)>
> Author: gregkh@suse.de <gregkh@suse.de>
> Author: Greg Kroah-Hartman <gregkh@suse>
> Author: Greg Kroah-Hartman <gregkh@suse.de>
> Author: Greg Kroah-Hartman <greg@kroah.com>
>
> I don't see an obvious way to do this with git, but it would be neat
> to have a 'clean' option on git log that would take each email address
> (author, signed-off, acked, etc) and map it through a table which
> would convert old email addresses in to the current one and also
> standardize the formatting of the names.
Something like .mailmap?
And to show the mapped author name instead of the committed one, you would
use "--pretty=format:%aN"? (Needs 1.6.0-rc0 at least, IIRC)
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-27 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 17:50 Cleaning up log messages Jon Smirl
2008-07-27 18:01 ` Johannes Schindelin [this message]
2008-07-27 18:16 ` Jon Smirl
2008-07-27 18:33 ` Petr Baudis
2008-07-27 19:07 ` Jon Smirl
2008-07-27 19:20 ` Johannes Schindelin
2008-07-27 19:31 ` Jon Smirl
2008-07-27 20:16 ` Johannes Schindelin
2008-07-27 18:47 ` Junio C Hamano
2008-07-27 20:52 ` Jon Smirl
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=alpine.DEB.1.00.0807272000270.5526@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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).