From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Liam Howlett <liam.howlett@oracle.com>,
"maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] maple_tree: Update copyright dates for test code
Date: Wed, 26 Oct 2022 05:43:14 -0700 [thread overview]
Message-ID: <f56da5f58afe5d759d16c7bdf3f748b683dfef32.camel@perches.com> (raw)
In-Reply-To: <Y1hR/RNpXB8O1sqZ@casper.infradead.org>
On Tue, 2022-10-25 at 22:15 +0100, Matthew Wilcox wrote:
> On Tue, Oct 25, 2022 at 01:40:19PM -0700, Joe Perches wrote:
> > Copyright reassignment not specified in commit message.
>
> It's not copyright reassignment. Liam has been an employee of Oracle
> for the entire duration. It is fixing the copyright notice to be correct.
Perhaps.
But it would definitely be better if the subject and message matched
the change.
All the suggested commit subject and message states is
> maple_tree: Update copyright dates for test code
and
> Add the span to the year of the development.
The patch itself does not do that.
On its face, it's reassigning copyright, not suggesting the original
copyright owner was in error.
prev parent reply other threads:[~2022-10-26 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 17:37 Liam Howlett
2022-10-25 18:06 ` Joe Perches
2022-10-25 20:23 ` Liam Howlett
2022-10-25 20:40 ` Joe Perches
2022-10-25 21:15 ` Matthew Wilcox
2022-10-26 12:43 ` Joe Perches [this message]
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=f56da5f58afe5d759d16c7bdf3f748b683dfef32.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=willy@infradead.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