From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: short log and email address
Date: Mon, 28 Jul 2008 20:11:40 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807282010190.8986@racer> (raw)
In-Reply-To: <9e4733910807281157u44c08a59ld3bdc0416e8a1d03@mail.gmail.com>
Hi,
On Mon, 28 Jul 2008, Jon Smirl wrote:
> On 7/28/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > On Mon, 28 Jul 2008, Jon Smirl wrote:
> >
> > > Using the -e option in shortlog changes the results by spitting
> > > things out by email address instead of leaving them combined by
> > > name. That's probably not what you want. Instead you want
> > > everything combined by name and then display the most recent email
> > > address used.
> >
> > What is so wrong with _not_ using -e (since you do not want to see the
> > email address stored in the commit message, and -e would be asking for
> > that _exactly_)?
>
> I wanted -e to give me the most recent email so that I would know how
> to sort the mailmap alias list.
As I explained, that is not what -e is _supposed_ to do. In Git, content
is king, and as such -e should look at the content. Unsurprisingly, that
is exactly what it does.
Nothing prohibits you from post-processing the output, though.
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-28 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 18:06 short log and email address Jon Smirl
2008-07-28 18:11 ` Mark Brown
2008-07-28 18:25 ` Jon Smirl
2008-07-29 10:22 ` Mark Brown
2008-07-28 18:34 ` Johannes Schindelin
2008-07-28 18:57 ` Jon Smirl
2008-07-28 19:11 ` Johannes Schindelin [this message]
2008-07-29 22:30 ` René Scharfe
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.0807282010190.8986@racer \
--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).