linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Martin Diehl <lists@mdiehl.de>, Adrian Bunk <bunk@fs.tum.de>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	andersen@codepoet.org, jgarzik@pobox.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Promise SATA driver GPL'd
Date: Wed, 23 Jul 2003 12:08:45 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10307231202520.13376-100000@master.linux-ide.org> (raw)
In-Reply-To: <1058965063.5516.41.camel@dhcp22.swansea.linux.org.uk>


Alan,

The simple flaw is present and pointed out in my inital statement.

GPL provides no means to enable the author/copyright holder to defend and
recover legal fees occurred during discovery and litigation.

What I find odd in you politics which stinks, is you and redhat are
pumping OSL into new features which are not generally submitted to the
standard base.  I do not care, but it does look funny.

Interesting points how the issues of holding the kernel to GPLv2 may
actually be a restriction to invalidate the actually license.  This tends
to make it possible for more arguements against the author when pursuing
violations.

Just a nickel to stir the pot.

Andre Hedrick
LAD Storage Consulting Group

On 23 Jul 2003, Alan Cox wrote:

> On Mer, 2003-07-23 at 13:32, Martin Diehl wrote:
> > If the copyright holder puts a note on his code saying it is released 
> > under version 2 of the GPL then clearly neither the "or any later" nor the 
> > "not specified" cases apply. And I really fail to see how one could 
> > argue this were an additional restriction compared to GPL v2 literally!
> 
> If the copyright holder is not permitted to make such a restriction and
> use the existing code then yes.
> 
> > Btw, you aren't saying linux-kernel would *not* come with a valid GPL, 
> > according to linux/COPYING, are you?
> 
> The kernel is under GPL. I'm not sure what Linus scribblings make change
> if anything. I understand why Linus did it "I dont want the FSF doing 
> something silly" and also why the FSF did it "so we can fix the license".
> 
> Ultimately it makes little difference, Linus is perfectly entitled to
> refuse to add anything that doesn't allow GPLv2 use to his kernel tree.
> 
> GPLv2 only effectively means your code becomes non-free if a flaw is
> found in that GPL revision, and nobody can fix it for 70 years so its
> an awkward trade off
> 
> I suspect this is getting offtopic 8)
> 


  reply	other threads:[~2003-07-23 19:04 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23  5:12 Promise SATA driver GPL'd Adam J. Richter
2003-07-23  5:28 ` Andre Hedrick
2003-07-23  9:08   ` Adrian Bunk
2003-07-23 10:12     ` Matthias Andree
2003-07-23 10:21       ` Wichert Akkerman
2003-07-23 11:47         ` Alan Cox
2003-07-23 11:54           ` Wichert Akkerman
2003-07-23 22:22           ` On "any later version" in GPL [Was: Re: Promise SATA driver GPL'd] Horst von Brand
2003-07-23 10:37       ` Promise SATA driver GPL'd Adrian Bunk
2003-07-23 10:29     ` Alan Cox
2003-07-23 10:51       ` Adrian Bunk
2003-07-23 11:43         ` Alan Cox
2003-07-23 12:17           ` Adrian Bunk
2003-07-23 12:32           ` Martin Diehl
2003-07-23 12:57             ` Alan Cox
2003-07-23 19:08               ` Andre Hedrick [this message]
2003-07-23 19:19                 ` Alan Cox
2003-07-23 19:33                   ` Andre Hedrick
2003-07-23 19:46                   ` Andre Hedrick
2003-07-23 20:59                 ` Roman Zippel
2003-07-23 22:22                   ` Andre Hedrick
2003-07-23 22:40                     ` Roman Zippel
2003-07-23 22:35                       ` Andre Hedrick
2003-07-23 23:02                         ` Roman Zippel
2003-07-23 23:08                           ` Andre Hedrick
2003-07-23 23:33                             ` Roman Zippel
2003-07-23 23:45                               ` Andre Hedrick
2003-07-24  0:14                                 ` dacin
2003-07-24  0:23                                   ` Andre Hedrick
2003-07-24  0:21                     ` David Schwartz
2003-07-24  0:21                       ` Andre Hedrick
2003-07-24 13:23                       ` Jesse Pollard
2003-07-24 14:01                         ` Richard B. Johnson
2003-07-24 18:37                         ` David Schwartz
2003-07-23 22:32                   ` Andre Hedrick
2003-07-23 22:46                     ` Larry McVoy
2003-07-23 23:13                       ` Roman Zippel
2003-07-23 10:40   ` Adam Sampson
  -- strict thread matches above, loose matches on Subject: below --
2003-07-22 18:45 Erik Andersen
2003-07-22 18:54 ` Jeff Garzik
2003-07-22 19:07   ` Erik Andersen
2003-07-22 19:39     ` Samuel Flory
2003-07-22 20:56     ` Jeff Garzik
2003-07-22 21:39       ` Erik Andersen
2003-07-22 23:25         ` Jeff Garzik
2003-08-27  3:01         ` Nick Urbanik
2003-08-27  3:14           ` Jeff Garzik
2003-08-27  9:00             ` Matthias Andree
2003-08-27 11:51               ` Jeff Garzik
2003-07-22 20:57     ` Jeff Garzik
2003-07-23 13:20     ` Mark Watts
2003-07-23  1:59 ` Andre Hedrick
2003-07-23  2:38   ` Shawn
2003-07-23 10:32   ` Alan Cox
2003-07-23 18:58     ` Andre Hedrick
2003-07-24 11:22       ` Matthias Andree
2003-08-13 13:34     ` Vojtech Pavlik
2003-08-13 14:24       ` Jeff Garzik
2003-08-15 10:17         ` Andre Hedrick
2003-07-25  3:44 ` Milan Roubal

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=Pine.LNX.4.10.10307231202520.13376-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andersen@codepoet.org \
    --cc=bunk@fs.tum.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@mdiehl.de \
    /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).