From: Guillem Jover <guillem@debian.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH] .mailmap: Reintroduce file to fix spelling and encoding issues
Date: Sun, 10 May 2026 19:22:04 +0200 [thread overview]
Message-ID: <20260510172205.350001-1-guillem@debian.org> (raw)
From: Guillem Jover <guillem@hadrons.org>
It make sense to use this file to fix spelling and encoding issues that
otherwise show up when checking the git history. It also makes sense to
honor name changes for people, to avoid dead naming or similar. As well
as fixing up local mail addresses that have never been valid.
It makes less sense to remap valid addresses at the time of submission
that represented a specific hat or organization, where the person is
no longer affiliated with, because that breaks the historic trail and
provenance of the changes. And is what require a continuous update
burden, which seems to have been the reason for the removal with
commit 2231a1659621d281a2fbb0d75bad5bccce538f96.
---
.mailmap | 7 +++++++
1 file changed, 7 insertions(+)
create mode 100644 .mailmap
diff --git a/.mailmap b/.mailmap
new file mode 100644
index 000000000..d58482666
--- /dev/null
+++ b/.mailmap
@@ -0,0 +1,7 @@
+# Fix name spelling and encoding issues.
+Adeodato Simó <dato@net.com.org.es>
+Américo Wang <xiyou.wangcong@gmail.com>
+André Goddard Rosa <andre.goddard@gmail.com>
+Bryan Østergaard <kloeri@exherbo.org>
+Nicolas François <nicolas.francois@centraliens.net>
+Reimar Döffinger <Reimar.Doeffinger@gmx.de>
--
2.53.0
next reply other threads:[~2026-05-10 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 17:22 Guillem Jover [this message]
2026-05-10 18:53 ` [PATCH] .mailmap: Reintroduce file to fix spelling and encoding issues Alejandro Colomar
2026-05-10 20:33 ` Guillem Jover
2026-05-10 21:40 ` Alejandro Colomar
2026-05-10 21:46 ` Alejandro Colomar
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=20260510172205.350001-1-guillem@debian.org \
--to=guillem@debian.org \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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