From: Chuck Lever III <chuck.lever@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Layton <jlayton@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsd: fix licensing header in filecache.c
Date: Mon, 31 Oct 2022 13:21:45 +0000 [thread overview]
Message-ID: <3C6909FD-6079-48AC-93E2-BD7937E31F86@oracle.com> (raw)
In-Reply-To: <Y1+A7XzxKbRCCH4z@infradead.org>
> On Oct 31, 2022, at 4:01 AM, Christoph Hellwig <hch@infradead.org> wrote:
>
> On Wed, Oct 26, 2022 at 10:35:18AM -0400, Jeff Layton wrote:
>> +// SPDX-License-Identifier: GPL-2.0
>> /*
>> - * Open file cache.
>> - *
>> - * (c) 2015 - Jeff Layton <jeff.layton@primarydata.com>
>> + * The NFSD open file cache.
>
> ЅPDX identifiers do not replace copyright statements. So while adding
> one is agood idea, dropping the copyright notice (if that counts as one)
> is not.
I know you are Not A Lawyer (tm), but:
The e-mail address in the copyright notice is stale. Is the convention
to leave stale e-mail addresses in place?
So I would expect copyright ownership of this code to go to Primary Data,
Jeff's employer at the time. But they don't exist now either; it might
be difficult to get permission from them to alter this notice.
--
Chuck Lever
next prev parent reply other threads:[~2022-10-31 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 14:35 [PATCH] nfsd: fix licensing header in filecache.c Jeff Layton
2022-10-26 14:36 ` Chuck Lever III
2022-10-31 8:01 ` Christoph Hellwig
2022-10-31 13:21 ` Chuck Lever III [this message]
2022-10-31 13:31 ` Christoph Hellwig
2022-10-31 13:48 ` Jeff Layton
2022-10-31 13:49 ` Chuck Lever III
2022-10-31 13:53 [PATCH] NFSD: Fix " Chuck Lever
2022-10-31 15:39 ` Jeff Layton
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=3C6909FD-6079-48AC-93E2-BD7937E31F86@oracle.com \
--to=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.