From: Kees Cook <keescook@chromium.org>
To: tools@kernel.org, Joe Perches <joe@perches.com>
Cc: Lee Jones <lee@kernel.org>, Bart Van Assche <bvanassche@acm.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: .mailmap support for removals (was Re: [PATCH 00/10] scsi: Replace {v}snprintf() variants with safer alternatives)
Date: Fri, 9 Feb 2024 22:56:06 -0800 [thread overview]
Message-ID: <202402092252.0A0A59A@keescook> (raw)
In-Reply-To: <20240208174912.GZ689448@google.com>
On Thu, Feb 08, 2024 at 05:49:12PM +0000, Lee Jones wrote:
> On Thu, 08 Feb 2024, Bart Van Assche wrote:
>
> > On 2/8/24 00:44, Lee Jones wrote:
> > > Cc: Andre Hedrick <andre@suse.com>
> >
> > Please take a look at https://lwn.net/Articles/508222/.
>
> get_maintainer.pl pulled it from here:
>
> https://github.com/torvalds/linux/blob/master/drivers/scsi/3w-xxxx.c#L11
Oh. Hm. It seems "git check-mailmap" (and get_maintainers.pl) don't
support a way to remove an email address -- only redirect it.
It seems we may want to support "don't use this email address" for more
than just the currently observed rationale. I don't have any good
suggestions for what the format should look like? Perhaps:
"" <address-to-remove@example.com>
?
--
Kees Cook
next parent reply other threads:[~2024-02-10 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240208084512.3803250-1-lee@kernel.org>
[not found] ` <c9129b08-50fb-4371-aa05-6f6c7cd7acfa@acm.org>
[not found] ` <20240208174912.GZ689448@google.com>
2024-02-10 6:56 ` Kees Cook [this message]
2024-02-10 22:56 ` .mailmap support for removals (was Re: [PATCH 00/10] scsi: Replace {v}snprintf() variants with safer alternatives) Joe Perches
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=202402092252.0A0A59A@keescook \
--to=keescook@chromium.org \
--cc=bvanassche@acm.org \
--cc=joe@perches.com \
--cc=lee@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tools@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).