* [Buildroot] .mailmap file for Buildroot?
@ 2026-10-22 21:42 Markus Mayer via buildroot
2026-10-22 22:46 ` Fiona Klute via buildroot
0 siblings, 1 reply; 4+ messages in thread
From: Markus Mayer via buildroot @ 2026-10-22 21:42 UTC (permalink / raw)
To: buildroot
[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]
Hi all,
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?
Thanks,
-Markus
[1] https://man7.org/linux/man-pages/man5/gitmailmap.5.html
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5469 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Buildroot] .mailmap file for Buildroot?
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
0 siblings, 1 reply; 4+ messages in thread
From: Fiona Klute via buildroot @ 2026-10-22 22:46 UTC (permalink / raw)
To: Markus Mayer, buildroot
Am 22.10.26 um 23:42 schrieb Markus Mayer via buildroot:
> Hi all,
>
> 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. :-)
Best regards,
Fiona
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Buildroot] .mailmap file for Buildroot?
2026-10-22 22:46 ` Fiona Klute via buildroot
@ 2026-10-23 7:29 ` Thomas Petazzoni via buildroot
2026-10-26 19:26 ` Markus Mayer via buildroot
0 siblings, 1 reply; 4+ messages in thread
From: Thomas Petazzoni via buildroot @ 2026-10-23 7:29 UTC (permalink / raw)
To: Fiona Klute; +Cc: Markus Mayer, buildroot
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Buildroot] .mailmap file for Buildroot?
2026-10-23 7:29 ` Thomas Petazzoni via buildroot
@ 2026-10-26 19:26 ` Markus Mayer via buildroot
0 siblings, 0 replies; 4+ messages in thread
From: Markus Mayer via buildroot @ 2026-10-26 19:26 UTC (permalink / raw)
To: Thomas Petazzoni; +Cc: Fiona Klute, buildroot
[-- Attachment #1.1: Type: text/plain, Size: 1340 bytes --]
On Fri, 23 Oct 2026 at 00:29, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> 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.
Thanks for the feedback. I sent a patch with .mailmap a few minutes ago.
Regards,
-Markus
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5469 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-10-26 19:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-10-26 19:26 ` Markus Mayer via buildroot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox