From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@yhbt.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id AD5FC1F66E;
	Tue, 18 Aug 2020 02:22:22 +0000 (UTC)
Date: Tue, 18 Aug 2020 02:22:22 +0000
From: Eric Wong <e@yhbt.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: meta@public-inbox.org
Subject: Re: Could public-inbox do something helpful with .mailmap?
Message-ID: <20200818022222.GA27878@dcvr>
References: <87ft8k69ce.fsf@x220.int.ebiederm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87ft8k69ce.fsf@x220.int.ebiederm.org>
List-Id: <meta.public-inbox.org>

"Eric W. Biederman" <ebiederm@xmission.com> wrote:
> 
> I just dug up some old emails and I got at least one persons current
> email address wrong because they have changed their email address
> frequently.
> 
> They have an update to their preferred email address in the .mailmap
> in the linux-kernel source.  Is there any chance public-inbox could
> look at .mailmap and do something useful in the web interface?

Yup.

> Perhaps display an alternate address next to the original?

I was thinking about updating the mailto: links and "reply"
instructions for git-send-email.

> I don't even know if that is a sensible request but I thought I would
> ask before I am distracted by something else.

It's been in the TODO for ages :)

Configuring it is the tough part: being able to group it so it
affects certain lists + projects, and prioritizations in case of
address conflicts across different projects, etc; yet being able
to share them (e.g. across all kernel-related lists, especially
if it's employer-dependent for some projects).

I'm working on inbox grouping right now for searching across
multiple (or all) inboxes, so this will tie into that.

The tricky part is making configuration sensible (because the
target is to support over 30K inboxes(!))