From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Mark Brown" <broonie@sirena.org.uk>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: short log and email address
Date: Mon, 28 Jul 2008 14:25:23 -0400 [thread overview]
Message-ID: <9e4733910807281125m7e555377l89cb57dff0f57ee2@mail.gmail.com> (raw)
In-Reply-To: <20080728181101.GA9148@sirena.org.uk>
On 7/28/08, Mark Brown <broonie@sirena.org.uk> wrote:
> On Mon, Jul 28, 2008 at 02:06:06PM -0400, 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.
>
> Apart from anything else you're assuming that people's names are
> globally unique - they aren't. I'm aware of several Mark Browns active
> in the free software world, for example.
There is a conflicting problem, multiple people with the same name and
people using multiple email addresses. The only solution I can see is
for the Mark Brown developers to get together and come up with a way
to differentiate their signatures (initial, nickname, etc), otherwise
I can't tell them apart from someone using multiple email addresses.
Mark Brown <broonie@opensource.wolfsonmicro.com>
Mark Brown <broonie@sirena.org.uk>
Same or two different people? These two names have committed to the kernel.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-07-28 18:26 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 [this message]
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
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=9e4733910807281125m7e555377l89cb57dff0f57ee2@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=broonie@sirena.org.uk \
--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.
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).