From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v2] batman-adv: Use mailmap to fix old e-mail addresses
Date: Wed, 8 Jan 2025 14:50:45 +0100 [thread overview]
Message-ID: <Z36CtUlH-_1GLts_@sellars> (raw)
In-Reply-To: <20250107-mailmap-v2-1-12d85da0b8e7@narfation.org>
On Tue, Jan 07, 2025 at 05:18:40PM +0100, Sven Eckelmann wrote:
> The .mailmap is used by git-(short)log to fix some botchered names and to
> map contributions from old e-mail addresses to new ones. It is also used by
> some tools to get the correct e-mail address for reviewers based on old
> contributions.
>
> The list was generated using old e-mail address changes in the source code.
> Also relevant entries for other contributors from the v6.13-rc5 release
> were added.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> [...]
> +Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@acsom.ch>
> +Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@ascom.ch>
> +Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@web.de>
> +Linus Lüssing <linus.luessing@c0d3.blue> <ll@simonwunderlich.de>
> +Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@web.de>
> [...]
There seem to be duplicate entries for me in there, both for the
@ascom.ch and @web.de addresses?
I've also submitted a patch to the Linux kernel for my old
ll@simonwunderlich.de address here now, thanks for notifying:
https://lore.kernel.org/linux-kernel/20250108035840.25194-1-linus.luessing@c0d3.blue/
Regards, Linus
next prev parent reply other threads:[~2025-01-08 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 16:18 [PATCH v2] batman-adv: Use mailmap to fix old e-mail addresses Sven Eckelmann
2025-01-08 13:50 ` Linus Lüssing [this message]
2025-01-08 13:56 ` Sven Eckelmann
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=Z36CtUlH-_1GLts_@sellars \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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