From: "Theodore Ts'o" <tytso@mit.edu>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@redhat.com>,
xfs <linux-xfs@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Date: Tue, 7 Nov 2017 14:15:26 -0500 [thread overview]
Message-ID: <20171107191526.x3rzfcnnlmaz264d@thunk.org> (raw)
In-Reply-To: <20171107184658.56b87d41@alans-desktop>
On Tue, Nov 07, 2017 at 06:46:58PM +0000, Alan Cox wrote:
> > Given that it had no license text on it at all, it "defaults" to GPLv2,
> > so the GPLv2 SPDX identifier was added to it.
> >
> > No copyright was changed, nothing at all happened except we explicitly
> > list the license of the file, instead of it being "implicit" before.
>
> Well if Christoph owns the copyright (if there is one) and he has stated
> he believes it is too trivial to copyright then it needs an SPDX tag that
> indicates the rightsholder has stated it's too trivial to copyright and
> (by estoppel) revoked any right they might have to pursue a claim.
If Cristoph has revoked any right to pursue a claim, then he's also
legally given up the right to complain if, say, Bradley Kuhn starting
distributing a version with a GPLv3 permission statement --- or if Greg
K-H adds a GPLv2 SPDX identifier. :-)
- Ted
> I'm sure there's a correct SPDX tag for that ;-)
>
> Alan
next prev parent reply other threads:[~2017-11-07 19:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171107020607.GA26910@magnolia>
2017-11-07 7:20 ` Christoph Hellwig
2017-11-07 7:39 ` Greg Kroah-Hartman
2017-11-07 17:07 ` Alan Cox
2017-11-07 17:12 ` Greg Kroah-Hartman
2017-11-07 17:25 ` Alan Cox
2017-11-07 18:30 ` Greg Kroah-Hartman
2017-11-07 17:20 ` Darrick J. Wong
2017-11-07 18:29 ` Greg Kroah-Hartman
2017-11-07 18:46 ` Alan Cox
2017-11-07 19:15 ` Theodore Ts'o [this message]
2017-11-07 19:28 ` Christoph Hellwig
2017-11-07 20:26 ` Greg Kroah-Hartman
2017-11-07 21:42 ` Luis R. Rodriguez
2017-11-08 6:37 ` Greg Kroah-Hartman
2017-11-08 17:19 ` Alan Cox
2017-11-08 18:46 ` Darrick J. Wong
2017-11-09 8:19 ` Greg Kroah-Hartman
2017-11-08 12:35 ` Philippe Ombredanne
2017-11-08 15:11 ` Christoph Hellwig
2017-11-08 18:06 ` Christoph Hellwig
2017-11-09 8:23 ` Greg Kroah-Hartman
2017-11-09 8:53 ` Christoph Hellwig
2017-11-22 17:07 ` Pavel Machek
2017-11-22 17:53 ` Greg Kroah-Hartman
2017-11-25 19:12 ` Pavel Machek
2017-11-25 21:57 ` Joe Perches
2017-11-27 16:50 ` Darrick J. Wong
2017-11-22 16:19 ` Pavel Machek
2017-11-08 23:47 ` Dave Chinner
2017-11-09 8:16 ` Greg Kroah-Hartman
2017-11-10 21:10 ` Alan Cox
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=20171107191526.x3rzfcnnlmaz264d@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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
all inboxes | Powered by JetHome®