From: Bradley Morgan <bradley.morgan@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Bradley Morgan <bradley.morgan@linux.dev>
Subject: [PATCH] mailmap: update email address for Bradley Morgan
Date: Mon, 9 Nov 2026 19:19:28 +0000 [thread overview]
Message-ID: <20261109191928.3222846-1-bradley.morgan@linux.dev> (raw)
I switched to bradley.morgan@linux.dev for kernel work, so map the
brads@mainlining.org and include@grrlz.net addresses over to keep
shortlog and blame from splitting commits between them.
Signed-off-by: Bradley Morgan <bradley.morgan@linux.dev>
---
Andrew: Could you *please* merge so it gets PRed quicker,
it will be a pain to wait for merge window... gitwise
---
.mailmap | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.mailmap b/.mailmap
index 0d05be949eff9..b277d0d04ac56 100644
--- a/.mailmap
+++ b/.mailmap
@@ -180,7 +180,8 @@ Boris Brezillon <bbrezillon@kernel.org> <b.brezillon.dev@gmail.com>
Boris Brezillon <bbrezillon@kernel.org> <b.brezillon@overkiz.com>
Boris Brezillon <bbrezillon@kernel.org> <boris.brezillon@bootlin.com>
Boris Brezillon <bbrezillon@kernel.org> <boris.brezillon@free-electrons.com>
-Bradley Morgan <brads@mainlining.org> <include@grrlz.net>
+Bradley Morgan <bradley.morgan@linux.dev> <brads@mainlining.org>
+Bradley Morgan <bradley.morgan@linux.dev> <include@grrlz.net>
Brendan Higgins <brendan.higgins@linux.dev> <brendanhiggins@google.com>
Brendan Jackman <brendan.jackman@linux.dev> <jackmanb@google.com>
Brian Avery <b.avery@hp.com>
--
2.53.0
next reply other threads:[~2026-11-09 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 19:19 Bradley Morgan [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-25 15:11 [PATCH] mailmap: update email address for Bradley Morgan Bradley Morgan
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=20261109191928.3222846-1-bradley.morgan@linux.dev \
--to=bradley.morgan@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.