From: Phil Hord <phil.hord@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Taylor Blau <me@ttaylorr.com>,
Ariadne Conill <ariadne@dereferenced.org>,
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: Fri, 9 Aug 2019 10:39:10 -0700 [thread overview]
Message-ID: <CABURp0q-gfXWiembsHYZb9bxhKrd6=zJA2bfQek0JDxeEP1HGA@mail.gmail.com> (raw)
In-Reply-To: <20190809114148.GB3957@sigill.intra.peff.net>
On Fri, Aug 9, 2019 at 4:41 AM Jeff King <peff@peff.net> wrote:
>
> On Thu, Aug 08, 2019 at 08:07:36PM -0700, Phil Hord wrote:
>
> > 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.
>
> Since the set of hash inputs is finite and small (i.e., the set of all
> emails in the repository), it would be trivial to generate the plaintext
> mapping from even a cryptographically strong hashed mapping.
>
> Which isn't to say it's _totally_ worthless, since that adds an extra
> step, but it really is just obfuscating the data.
Yes, obfuscation is all I expect. Someone who needs deeper scrubbing
will need to rewrite their history instead.
next prev parent reply other threads:[~2019-08-09 17:39 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
2019-08-09 11:21 ` Taylor Blau
2019-08-09 11:41 ` Jeff King
2019-08-09 17:39 ` Phil Hord [this message]
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='CABURp0q-gfXWiembsHYZb9bxhKrd6=zJA2bfQek0JDxeEP1HGA@mail.gmail.com' \
--to=phil.hord@gmail.com \
--cc=ariadne@dereferenced.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).