From: Ariadne Conill <ariadne@dereferenced.org>
To: Phil Hord <phil.hord@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
Git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2019, #06; Thu, 25)
Date: Thu, 8 Aug 2019 22:21:02 -0500 [thread overview]
Message-ID: <CAAOiGNzuLu26H56RvNCT=1iPQWOtGQJACO-pS8azerUio--=tw@mail.gmail.com> (raw)
In-Reply-To: <CABURp0oFNWfWEwnkjV1+Tag91HTRBCaJjyvc8CXtPGu78DhtSw@mail.gmail.com>
Hello,
On Thu, Aug 8, 2019 at 10:07 PM Phil Hord <phil.hord@gmail.com> wrote:
>
> The issue of deadnaming aside, turning on log.mailmap by default is
> the sensible thing to do given that other Git features already honor
> it that way. Having it ignored-by-default (but only sometimes) just
> adds confusion when a mailmap is available.
This is my point exactly! My motive for improving this behaviour is
entirely irrelevant, honestly. I regret ever bringing it up elsewhere
in the discussions, as it's completely irrelevant.
> > > > - The '.mailmap' provides a list of transgender individuals, along
> > > > with their deadname, which can be used to harass them.
> > >
> > > This is potentially a problem but it's not as bad as you depict. A
> > > mailmap rule can match against e-mail only, which is precisely what I
> > > have done in my projects.
> >
> > Ah, I may be severely mistaken -- my memory was that '.mailmap'
> > rewriting could be used to rewrite both name and email, not merely
> > email. I thought that records could take:
> >
> > A U Thor <author@xample.com> -> B C Xyzz <newname@example.com>
> >
> > instead of canonicalizing by email alone. If this is the case, then I
> > completely agree and share the opinion that this is not as bad as I
> > originally depicted.
>
> The long form you give there is to be used in case the old email
> address is not a unique key. See 'git help shortlog'.
>
> The problem we have at work is that one woman's old email address
> includes her deadname, like <firstname.lastname@company.com>. I will
> leave it up to her whether she chooses to be listed explicitly in the
> mailmap. I have wondered if we should permit hashed email addresses
> to be used for this specific case, but this also has its drawbacks.
I'd be open to looking into adding support for hashing the e-mail for
cases like this if people are interested. The
firstname.lastname@company.com case is certainly a tough one to crack
otherwise, but I think that a solution that works for most cases still
is useful. In the meantime, I think it makes sense to let people
decide whether they wish to use mailmap for this purpose, based on
their own understanding of the risks involved.
Ariadne
next prev parent reply other threads:[~2019-08-09 3:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 0:19 What's cooking in git.git (Jul 2019, #06; Thu, 25) Junio C Hamano
2019-07-26 14:33 ` Johannes Schindelin
2019-07-26 20:23 ` Junio C Hamano
2019-07-27 19:38 ` Rohit Ashiwal
2019-07-27 20:40 ` Elijah Newren
2019-07-27 20:57 ` Rohit Ashiwal
2019-07-27 21:42 ` Elijah Newren
2019-07-28 20:34 ` Carlo Arenas
2019-08-09 0:13 ` Taylor Blau
2019-08-09 1:34 ` Ariadne Conill
2019-08-09 2:07 ` Taylor Blau
2019-08-09 3:04 ` Ariadne Conill
2019-08-09 3:07 ` Phil Hord
2019-08-09 3:21 ` Ariadne Conill [this message]
2019-08-09 11:21 ` Taylor Blau
2019-08-09 11:41 ` Jeff King
2019-08-09 17:39 ` Phil Hord
2019-08-09 14:06 ` Randall S. Becker
2019-08-09 16:29 ` Jeff King
2019-08-09 16:32 ` Randall S. Becker
2019-08-09 17:45 ` Junio C Hamano
2019-08-09 18:05 ` Phil Hord
2019-08-10 6:10 ` Jeff King
2019-08-12 0:39 ` Junio C Hamano
2019-08-12 13:39 ` Randall S. Becker
2019-08-09 17:44 ` Junio C Hamano
2019-08-09 19:06 ` Randall S. Becker
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='CAAOiGNzuLu26H56RvNCT=1iPQWOtGQJACO-pS8azerUio--=tw@mail.gmail.com' \
--to=ariadne@dereferenced.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=phil.hord@gmail.com \
/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).