[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202209271710.6DD4B44C@keescook>
Date: Tue, 27 Sep 2022 17:11:08 -0700
From: Kees Cook <keescook@...omium.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Geert Stappers <stappers@...ppers.nl>,
Linus Torvalds <torvalds@...ux-foundation.org>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, patches@...ts.linux.dev,
Jarkko Sakkinen <jarkko@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Maciej Falkowski <maciej.falkowski9@...il.com>
Subject: Re: [PATCH v10 27/27] MAINTAINERS: Rust
On Tue, Sep 27, 2022 at 05:53:12PM +0200, Miguel Ojeda wrote:
> On Tue, Sep 27, 2022 at 5:34 PM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > How about just fixing up the emails in these patches, which will keep us
> > from having bouncing ones for those of us who do not use the .mailmap
> > file.
>
> Sorry about that...
>
> One question: if somebody wants to keep the Signed-off-bys and/or Git
> authorship information using the old email for the patches (except the
> `MAINTAINERS` entry), is that OK? (e.g. maybe because they did most of
> the work in their previous company).
IMO, the S-o-b's should stand since they're historical, but fixing
MAINTAINERS to be up-to-date makes sense.
--
Kees Cook
Powered by blists - more mailing lists