From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Bdale Garbee <bdale@hp.com>,
Grant Grundler <grundler@parisc-linux.org>,
Adrian Bunk <bunk@kernel.org>,
kyle@mcmartin.ca, linux-parisc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] binfmt_som.c: add MODULE_LICENSE
Date: Sun, 10 Aug 2008 18:05:35 -0600 [thread overview]
Message-ID: <20080811000535.GB14163@colo.lackof.org> (raw)
In-Reply-To: <20080810151433.GO8618@parisc-linux.org>
On Sun, Aug 10, 2008 at 09:14:33AM -0600, Matthew Wilcox wrote:
...
> > If that is indeed the timing, I agree. If not, let me know, and I'll
> > see if I can push the right buttons in HP.
>
> http://cvs.parisc-linux.org/obsolete/linux-2.2/fs/binfmt_som.c?rev=1.8&view=log
>
> indicates I first committed the file in June 1999 and was the majority
> committer to this file (prumpf also committed some code). My last
> commit to it was in November 1999 (while I still worked for Genedata).
Ok - I didn't realize that.
> At some point around then, we moved to the 2.4 CVS tree:
>
> http://cvs.parisc-linux.org/linux-2.4/fs/binfmt_som.c?rev=1.21&view=log
>
> and there are some commits from other people at HP and myself while at
> Linuxcare and HP.
Thanks for digging this up.
I expect it should be easy for Bdale to get this rubber stamped
by any one of the HP linux kernel engineers. HP legal shouldn't
need to be involved.
>
> The 2.5 development tree:
> http://cvs.parisc-linux.org/linux-2.5/fs/binfmt_som.c?rev=1.3&view=log
>
> doesn't show anything of great interest.
>
> and the 2.6 tree represents accurately how much effort we put into SOM:
> http://cvs.parisc-linux.org/linux-2.6/fs/binfmt_som.c?rev=1.8&view=log
>
>
> So while HP has a legitimate claim to some parts of the file, my initial
> contributions before I worked for Linuxcare or HP were the largest and I
> don't think that anyone has a legitimate claim that this is not a
> derived work of GPL code, and hence I think Adrian's patch should be
> accepted.
I agree and apologize for my bad memory and lazy attitude. I didn't mean
to make a big deal of this - just assumed HP was the right party to
address this to.
cheers,
grant
>
> --
> 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 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 21:11 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 [this message]
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
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=20080811000535.GB14163@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=akpm@linux-foundation.org \
--cc=bdale@hp.com \
--cc=bunk@kernel.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
/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®