From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: short log and email address
Date: Wed, 30 Jul 2008 00:30:01 +0200 [thread overview]
Message-ID: <488F99E9.2010806@lsrfire.ath.cx> (raw)
In-Reply-To: <9e4733910807281157u44c08a59ld3bdc0416e8a1d03@mail.gmail.com>
Jon Smirl schrieb:
> On 7/28/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>> Hi,
>>
>>
>> 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.
<snip>
> If the name isn't in mailmap, tell them to make a patch adding their
> name or to change their name.
That makes sense if you want to list all contributors in .mailmap...
> If the name is there but the email is not the last one in the list,
> tell them to make a patch rearranging mailmap to reflect their current
> name/email.
... but why would you want to check if they used their respective email
entry that is sorted last in the file? A person might have multiple
current email addresses, e.g. someone could send patches for one
subsystem from work and patches for something else from home, as a hobby.
René
prev parent reply other threads:[~2008-07-29 22:31 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
2008-07-29 22:30 ` René Scharfe [this message]
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=488F99E9.2010806@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=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.
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 NNTP newsgroup(s).