From: Theodore Tso <tytso@mit.edu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Josef Bacik <josef@redhat.com>,
linux-fsdevel@vger.kernel.org, sandeen@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] fiemap tester
Date: Mon, 11 May 2009 15:30:36 -0400 [thread overview]
Message-ID: <20090511193036.GE21518@mit.edu> (raw)
In-Reply-To: <4A08666A.6020700@oracle.com>
On Mon, May 11, 2009 at 10:54:50AM -0700, Randy Dunlap wrote:
>
> Given that we are not lawyers:
>
> The current kernel tree contains >3500 files that contain the phrase
> "All Rights Reserved". Are they a problem?
Yes, but how many of them are followed with a GPL licensing statement?
And presumably we have a signed-off-by chain that which includes
someone asserting that they have followed the Developer's
Certification of Origin rules. (That being said, it's usually better
if the All Rights Reserved is removed, after getting explicit
permission from the original copyright owner to make it available
under a GPLv2 license.)
The issue with the xfstests tree is the *only* copyright permission
statement is "All Rights Reserved", and while there is an oral
assertion from SGI that it was supposed to be released under an open
source license, there is nothing in writing or in the source
distribution indicating this, and it wasn't clear to me whether this
oral assurance happened before or after SGI was purchased by
Rackspace.
- Ted
next prev parent reply other threads:[~2009-05-11 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 19:16 [RFC] fiemap tester Josef Bacik
2009-05-08 23:13 ` Andrew Morton
2009-05-11 9:46 ` Christoph Hellwig
2009-05-11 15:14 ` Eric Sandeen
2009-05-11 17:10 ` Theodore Tso
2009-05-11 17:46 ` Eric Sandeen
2009-05-11 17:54 ` Randy Dunlap
2009-05-11 19:30 ` Theodore Tso [this message]
2009-05-11 17:13 ` Andrew Morton
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=20090511193036.GE21518@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).