On Fri, Aug 9, 2019 at 4:41 AM Jeff King <p...@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.lastn...@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.
