From: Matthew Wilcox <matthew@wil.cx>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Adrian Bunk <bunk@kernel.org>,
grundler@parisc-linux.org, kyle@mcmartin.ca,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, bdale@hp.com
Subject: Re: [2.6 patch] binfmt_som.c: add MODULE_LICENSE
Date: Mon, 11 Aug 2008 11:11:36 -0600 [thread overview]
Message-ID: <20080811171136.GS8618@parisc-linux.org> (raw)
In-Reply-To: <20080811145652.100E74E77@hiauly1.hia.nrc.ca>
On Mon, Aug 11, 2008 at 10:56:51AM -0400, John David Anglin wrote:
> This file was included before the SCO situation arose. The copyright
> notice is similar to most. Checking 2.6.22.19, I see that more than
> half the .c files lack MODULE_LICENSE("GPL") lines.
>
> I don't understand why we are talking about HP here. According to
> Matthew, his last commit to this file occured while he worked for
> Genedata.
Whoops, that was in the linux-2.2 CVS repository. There were subsequent
commits in the 2.4/2.5/2.6 repositories, some of which HP might have
a claim to.
> It is my understanding that copyright normally acrues
> to employers in employment situations. If Matthew was an employee
> and not an independent contractor at the time, then why are we not
> talking about Genedata, or its subsequent owner?
While I don't have a copy of my employment contract with Genedata any
more, my recollection is that they did not claim copyright on works I
produced that were off company time. It would be governed by Swiss law
which I believe would not permit such a term in the contract.
> Subsequent
> employment at HP or their funding of the parisc port shouldn't
> affect the licensing of a file that was previously contributed.
That's my basic argument. If binfmt_elf had contained the GPL
boilerplate, I would have copied that when creating binfmt_som. It was
intended to be GPL, it was a derivative work of GPL file (that also
didn't explicitly state it was GPL), it has been treated as GPL for
almost a decade.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-08-11 17:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 21:11 [2.6 patch] binfmt_som.c: add MODULE_LICENSE Adrian Bunk
2008-08-10 0:55 ` Grant Grundler
2008-08-10 1:00 ` Matthew Wilcox
2008-08-10 13:41 ` Bdale Garbee
2008-08-10 15:14 ` Matthew Wilcox
2008-08-11 0:05 ` Grant Grundler
2008-08-11 14:15 ` Bdale Garbee
2008-08-10 14:11 ` Adrian Bunk
2008-08-11 0:10 ` Grant Grundler
2008-08-11 10:46 ` Adrian Bunk
2008-08-11 14:56 ` John David Anglin
2008-08-11 15:51 ` Adrian Bunk
2008-08-11 16:56 ` John David Anglin
2008-08-11 18:43 ` Adrian Bunk
2008-08-11 17:11 ` Matthew Wilcox [this message]
2008-08-15 21:44 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2008-06-15 16:13 Adrian Bunk
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=20080811171136.GS8618@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=bdale@hp.com \
--cc=bunk@kernel.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox