linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Theodore Ts'o <tytso@mit.edu>,
	Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
	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: Wed, 22 Nov 2017 17:19:28 +0100	[thread overview]
Message-ID: <20171122161927.GC12684@amd> (raw)
In-Reply-To: <20171107191526.x3rzfcnnlmaz264d@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

On Tue 2017-11-07 14:15:26, Theodore Ts'o wrote:
> 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.  :-)

Yes, maybe Greg can legaly do that. That does not make it good
idea... and we have higher standards than "not illegal in most
countries" :-).

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2017-11-22 16:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  2:06 [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license Darrick J. Wong
2017-11-07  7:20 ` WTF? " 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
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 [this message]
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=20171122161927.GC12684@amd \
    --to=pavel@ucw.cz \
    --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 \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).