From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Markus Mayer <markus.mayer@broadcom.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] .mailmap file for Buildroot?
Date: Fri, 23 Oct 2026 09:29:10 +0200 [thread overview]
Message-ID: <atsMtHazGzkiwaXR@windsurf> (raw)
In-Reply-To: <69c73771-8203-4c26-9a6c-0f7a5940c519@gmx.de>
On Fri, Oct 23, 2026 at 12:46:23AM +0200, Fiona Klute via buildroot wrote:
> > I was recently faced with the misfortune that my long-standing e-mail
> > address dating back to 2012 (mmayer@broadcom.com) was discontinued and
> > no longer works. Of course, I can adjust my submissions going forward,
> > but existing patches are stuck with the old e-mail address, which can
> > be confusing, since messages sent to that address will bounce.
> >
> > The Linux kernel has a .mailmap file for this purpose. This is a
> > standard feature supported by Git[1] that helps with remapping e-mail
> > addresses in situations just like this one. Would it make sense to
> > introduce this mechanism for Buildroot, as well? Surely my e-mail
> > address is neither the first nor the only one that has gone away over
> > the years without the person also disappearing. So my feeling is this
> > might be useful in general.
> >
> > What are your thoughts?
> I don't see why not, it's not fundamentally different from updating a
> DEVELOPERS entry. Just send a patch with the mapping you need. :-)
Agreed, it makes sense to me as well.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-23 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 21:42 [Buildroot] .mailmap file for Buildroot? Markus Mayer via buildroot
2026-10-22 22:46 ` Fiona Klute via buildroot
2026-10-23 7:29 ` Thomas Petazzoni via buildroot [this message]
2026-10-26 19:26 ` Markus Mayer via buildroot
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=atsMtHazGzkiwaXR@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=markus.mayer@broadcom.com \
--cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox