git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Gwyneth Morgan <gwymor@tilde.club>, Fangyi Zhou <me@fangyi.io>,
	git@vger.kernel.org
Subject: Re: [PATCH] .mailmap: Update mailmap
Date: Sat, 11 Sep 2021 10:52:40 -0400	[thread overview]
Message-ID: <YTzCuAWCJESyxIfU@coredump.intra.peff.net> (raw)
In-Reply-To: <87czpfc2j6.fsf@evledraar.gmail.com>

[culling cc list as earlier]

On Sat, Sep 11, 2021 at 03:31:49AM +0200, Ævar Arnfjörð Bjarmason wrote:

> Whereas most if not all edits to this file are likely to be janitorial
> work such as de-duplicating E-Mail addresses, or cases where the people
> involved even if they can't be contacted have already shared this
> information unambiguously with the world, it just happens to be in the
> mailing list archive, not in .mailmap.
> 
> E.g. I'd think these were fine, even assuming you can't contact the
> parties involved:
> 
>  * The ML history reveals someone who's clearly the same person was
>    using N E-Mail addresses in succession, we should probably map it all
>    to the latest one, unclutters shortlog and the like.

Just playing devil's advocate for a moment. What about people who have
used two different identities because they were contributing in two
different capacities (say, one from a work email, where they want to
continue to credit that entity, and then later from a personal email).

That works against the goal of "you can easily email the person from an
old commit". But it seems reasonable to respect their wishes there
(e.g., they may not _want_ to deal with old contributions submitted
as part of work).

The root of the problem is that we don't know their wishes, so we are
making an assumption when a third party proposes the change.

-Peff

  reply	other threads:[~2021-09-11 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 13:02 [PATCH] .mailmap: Update mailmap Fangyi Zhou
2021-09-10 15:22 ` Gwyneth Morgan
2021-09-10 15:31   ` Jeff King
2021-09-10 15:35     ` Sibi Siddharthan
2021-09-11  0:32     ` Junio C Hamano
2021-09-11  1:31       ` Ævar Arnfjörð Bjarmason
2021-09-11 14:52         ` Jeff King [this message]
2021-09-11 14:47       ` Jeff King
2021-09-10 16:48   ` Oddidies in the .mailmap parser & future syntax extensions Ævar Arnfjörð Bjarmason
2021-09-10 18:11     ` Junio C Hamano
2021-09-10 19:50       ` Ævar Arnfjörð Bjarmason
2021-09-10 20:20         ` Junio C Hamano
2021-09-13  4:02           ` Ævar Arnfjörð Bjarmason

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=YTzCuAWCJESyxIfU@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gwymor@tilde.club \
    --cc=me@fangyi.io \
    /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).