From: Liam Howlett <liam.howlett@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: "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: Tue, 25 Oct 2022 20:23:13 +0000 [thread overview]
Message-ID: <20221025202305.pyzau7vzvkizqbir@revolver> (raw)
In-Reply-To: <8d8a291b5237750827d6847b29efde5b750a28f7.camel@perches.com>
* Joe Perches <joe@perches.com> [221025 14:06]:
> On Tue, 2022-10-25 at 17:37 +0000, Liam Howlett wrote:
> > Add the span to the year of the development.
> >
> > Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> > ---
> > tools/testing/radix-tree/maple.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/radix-tree/maple.c b/tools/testing/radix-tree/maple.c
> > index 35082671928a..3620c9e5f7c5 100644
> > --- a/tools/testing/radix-tree/maple.c
> > +++ b/tools/testing/radix-tree/maple.c
> > @@ -1,7 +1,8 @@
> > // SPDX-License-Identifier: GPL-2.0+
> > /*
> > - * maple_tree.c: Userspace shim for maple tree test-suite
> > - * Copyright (c) 2018 Liam R. Howlett <Liam.Howlett@Oracle.com>
> > + * maple_tree.c: Userspace testing for maple tree test-suite
> > + * Copyright (c) 2018-2022 Oracle Corporation
> > + * Author: Liam R. Howlett <Liam.Howlett@Oracle.com>
>
> Confused here. Who owns the copyright from 2018?
2018 should have also been oracle on this file. Note the email
address.
>
> And what happened from 2019 through 2021 ?
Development continued which is why I wanted to extend the date to a
range. I also presented the maple tree and spoke to a lot of people
about it. Also a pandemic, I hear.
>
> $ git log --stat -p -1 54a611b605901c7d5d05b6b8f5d04a6ceb0962aa | grep -i copyright
> + * Copyright (c) 2018-2022 Oracle
> + * Copyright (c) 2018-2022 Oracle Corporation
> + * Copyright (c) 2018 Liam R. Howlett <Liam.Howlett@Oracle.com>
>
Right, this is what I am correcting. I'm not sure what you are getting
at here. Did I do something incorrect with trying to fix my mistake?
Thanks,
Liam
next prev parent reply other threads:[~2022-10-25 20:23 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 [this message]
2022-10-25 20:40 ` Joe Perches
2022-10-25 21:15 ` Matthew Wilcox
2022-10-26 12:43 ` 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=20221025202305.pyzau7vzvkizqbir@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.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