From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: <git@vger.kernel.org>
Subject: [PATCH 0/1] Hashed mailmap support
Date: Sun, 13 Dec 2020 01:05:38 +0000 [thread overview]
Message-ID: <20201213010539.544101-1-sandals@crustytoothpaste.net> (raw)
Many people, through the course of their lives, will change either a
name or an email address. For this reason, we have the mailmap, to map
from a user's former name or email address to their current, canonical
forms. Normally, this works well as it is.
However, sometimes people change a name (or an email) and want to
completely cease use of the former name or email. This could be because
a transgender person has transitioned, because a person has left an
abusive partner or broken ties with an abusive family member, or for any
other number of good and valuable reasons. In these cases, placing the
former name in the .mailmap may be undesirable.
For those situations, let's introduce a hashed mailmap, where the user's
former name or email address can be in the form @sha256:<hash>. This
obscures the former name or email.
Note that this is not perfect, because a user can simply look up all the
hashed values and find out the old values. However, for projects which
wish to adopt the feature, it can be somewhat effective to hash all
existing mailmap entries and include some no-op entries from other
contributors as well, so as to make this process less convenient.
I've spoken to a variety of folks about this, and while we all agree
this design isn't perfect, it is an improvement over the status quo. It
is obfuscation, not security, and in this case, I think that's fine.
I'm open to hearing ideas about how to improve this design if there are
any.
I welcome feedback on this patch, while encouraging people to be mindful
of our code of conduct.
brian m. carlson (1):
mailmap: support hashed entries in mailmaps
mailmap.c | 39 +++++++++++++++++++++++++++++++++++++--
t/t4203-mailmap.sh | 35 +++++++++++++++++++++++++++++++++++
2 files changed, 72 insertions(+), 2 deletions(-)
next reply other threads:[~2020-12-13 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 1:05 brian m. carlson [this message]
2020-12-13 1:05 ` [PATCH 1/1] mailmap: support hashed entries in mailmaps brian m. carlson
2020-12-13 9:34 ` Johannes Sixt
2020-12-13 9:45 ` Johannes Sixt
2020-12-13 20:38 ` brian m. carlson
2020-12-14 0:09 ` Junio C Hamano
2020-12-16 0:50 ` brian m. carlson
2020-12-14 11:54 ` Ævar Arnfjörð Bjarmason
2020-12-15 11:13 ` Phillip Wood
2020-12-15 1:48 ` [PATCH 0/1] Hashed mailmap support Jeff King
2020-12-15 2:40 ` Jeff King
2020-12-15 11:15 ` Phillip Wood
2020-12-18 2:29 ` brian m. carlson
2020-12-18 5:56 ` Jeff King
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=20201213010539.544101-1-sandals@crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--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.
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).