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?
Date: Tue, 18 Aug 2020 02:22:22 +0000 [thread overview]
Message-ID: <20200818022222.GA27878@dcvr> (raw)
In-Reply-To: <87ft8k69ce.fsf@x220.int.ebiederm.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(!))
prev parent reply other threads:[~2020-08-18 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 1:17 Could public-inbox do something helpful with .mailmap? Eric W. Biederman
2020-08-18 2:15 ` Konstantin Ryabitsev
2020-08-18 2:22 ` Eric Wong [this message]
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200818022222.GA27878@dcvr \
--to=e@yhbt.net \
--cc=ebiederm@xmission.com \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).