From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Florine W. Dekker" <florine@fwdekker.com>
Cc: demerphq <demerphq@gmail.com>, "René Scharfe" <l.s.r@web.de>,
Git <git@vger.kernel.org>
Subject: Re: Wildcards in mailmap to hide transgender people's deadnames
Date: Tue, 20 Sep 2022 00:32:01 +0000 [thread overview]
Message-ID: <YykKARz//2mENrRH@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <045e7914-ab16-4d5e-ea9d-8e3c7c758fff@fwdekker.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On 2022-09-16 at 16:59:23, Florine W. Dekker wrote:
> I understand what you mean, and agree that mailmap is just a workaround for
> this issue, having been designed to unify a user's multiple identifiers,
> rather than helping move on from a now-invalid identifier. Being completely
> new to this mailing list, however, I feel that solving the issues you raise
> might be a might much for me to take on.
I agree this is a bigger, separate issue that we should address, but it
shouldn't prevent us from doing what improvements we can to the mailmap.
> Instead, for now, I'm interested to see what we can do with mailmap as a
> workaround. I like the idea of using URL encoding, and would like to hear
> others' opinions on doing so. I think it provides a social signal on its
> obfuscated state, it prevents people from accidentally finding out, and is
> easy and efficient to execute.
I think this would be a fine solution. If folks think the hashed
mailmap would be better, I can resend that, or if we like the
URL-encoded option, that shouldn't be too difficult to implement.
I do appreciate you taking the time to bring this up since I think this
is an important issue to address and it's come up a couple of times. I
hope that this time we can come up with some sort of improvement with
the mailmap we're willing to take.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2022-09-20 0:32 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
2022-09-26 9:14 ` Ævar Arnfjörð Bjarmason
[not found] ` <CANgJU+Wt_yjv1phwiSUtLLZ=JKA9LvS=0UcBYNu+nxdJ_7d_Ew@mail.gmail.com>
2022-09-16 16:59 ` Florine W. Dekker
2022-09-20 0:32 ` brian m. carlson [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
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=YykKARz//2mENrRH@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=demerphq@gmail.com \
--cc=florine@fwdekker.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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).