mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: "Ævar Arnfjörð Bjarmason" <>
Cc: "brian m. carlson" <>,
	"Florine W. Dekker" <>,
	"René Scharfe" <>,
Subject: Re: Wildcards in mailmap to hide transgender people's deadnames
Date: Wed, 21 Sep 2022 09:42:31 -0700	[thread overview]
Message-ID: <xmqqh71065mw.fsf@gitster.g> (raw)
In-Reply-To: <> (=?utf-8?B?IsOG?= =?utf-8?B?dmFyIEFybmZqw7Zyw7A=?= Bjarmason"'s message of "Tue, 20 Sep 2022 12:23:05 +0200")

Ævar Arnfjörð Bjarmason <> writes:

> I think it would be irresponsible of us to provide a feature that looks
> as though it can in any way mitigate those concerns.
> If you're someone that's worried about being harassed if someone makes
> the link from your previous identity Y to your current identity X where
> you already have Y as part of a public git history. The right answer is
> to not submit a change to the .mailmap to explicitly connect the two.

While I agree with the sentiment "You are in control if your three
names appear to refer to the same person" (and "On the Internet
nobody knows you're a dog"), I wish the world were so black and

Many people change their names over the course of their life, and
some do not want the linkage to their past revealed.  Many of them
have nothing to be ashamed of themselves but do so due to risk of
discrimination, while some of them may do so to hide inconvenient
facts about their past.  While I have no sympathy to the latter, I
do not think it is unreasonable for the folks in the former camp to
also want recognition for the achievement made under their old as
well as their current identity.  And "pretend you have nothing to do
with that identity you used in the past life" goes directly against
the idea of taking credit for what you did in the past.

As the expertise you demonstrated under your old name will not
help others find you as an expert in an area, until your new name
starts being associated with your newly earned recognition, it is
also a loss for the development community.

I dunno.

  parent reply	other threads:[~2022-09-21 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 21:53 Wildcards in mailmap to hide transgender people's deadnames Florine W. Dekker
2022-09-14  7:40 ` René Scharfe
2022-09-14  9:07   ` Florine W. Dekker
2022-09-19 11:20     ` Ævar Arnfjörð Bjarmason
2022-09-19 12:27       ` rsbecker
2022-09-19 15:19       ` brian m. carlson
2022-09-19 16:31         ` Junio C Hamano
2022-09-19 17:26           ` brian m. carlson
2022-09-20 10:23         ` Ævar Arnfjörð Bjarmason
2022-09-20 14:58           ` Florine W. Dekker
2022-09-21 16:42           ` Junio C Hamano [this message]
2022-09-26  9:14             ` Ævar Arnfjörð Bjarmason
     [not found]   ` <>
2022-09-16 16:59     ` Florine W. Dekker
2022-09-20  0:32       ` brian m. carlson

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqh71065mw.fsf@gitster.g \ \ \ \ \ \ \

* 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

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).