mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <dhazelton@enter.net>
Cc: <espie@nerim.net>, <linux-kernel@vger.kernel.org>
Subject: RE: GPL weasels and the atheros stink
Date: Mon, 3 Sep 2007 17:23:37 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKOEGFGJAC.davids@webmaster.com> (raw)
In-Reply-To: <200709031343.23949.dhazelton@enter.net>


> Wrong - I said "You can't complain about Person A doing X when
> you let Person
> B do X without complaint".

Yes, I can. There is no inconsistency between acting in one case and failing
to act in another. We need not act in every possible case where we could act
to preserve our right to act in a particular case.

> To whit: you can't complain that Jiri has made
> changes to a dual-licensed "work" and only released his changes
> under one of
> the licenses on the work when somebody else - in this case Msr.
> Floeter - has
> done the same thing.

First of all, I haven't complained about Jiri's changes. Second, I most
certainly can. I can complain about one murder without complaining about
every murder. There is no inconsistency whatsoever with acting in one case
without having to act in every other conceivable case.

We can complain about or work to fight whatever injustices we like. There is
no obligation to address every equal, or greater, injustice before working
on the injustice of one's choice.

> No, no confusion. You could care less about the code being dual-licensed.
Your
> choice of subjects 'GPL weasels' speaks volumes.

*My* choice of subjects?! You seem to have me confused with someone else
entirely.

My sole points in this thread were to:

1) Correct some misunderstandings about how dual licenses actually work.

2) Explain *why* a file cannot really remain dual-licensed if it's part of
the Linux kernel distribution.

While I generally prefer the BSD license to the GPL license and tend to be a
pretty vocal GPL critic, I have said many times that almost any *consistent*
license is better for a large project than different licenses, even if
they're compatible, on different files.

> Doesn't matter if the BSD license or the GPL *PERMITS* it or not. The fact
> remains that the person making a work available under *ANY* form of
copyright
> license has the right to revoke said grant of license to anyone. The GPL
> codifies certain situations in which the person would not, personally,
have
> to revoke the license, but does not limit the original copyright holders
> rights (in that regard) in any way.

I'm not sure where you're getting this from, but it's not true. Linus cannot
decide tomorrow that nobody can distribute the Linux kernel anymore.

DS



  reply	other threads:[~2007-09-04  0:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02 14:03 Marc Espie
2007-09-02 16:52 ` Kyle Moffett
2007-09-02 16:54 ` Alan Cox
2007-09-02 17:16 ` Oleg Verych
2007-09-02 17:34 ` Michael Tharp
2007-09-02 17:41 ` Jeff Garzik
2007-09-02 17:57 ` Jeff Garzik
2007-09-02 20:22 ` Bernd Petrovitsch
2007-09-03  2:01 ` David Schwartz
2007-09-03  2:57   ` Daniel Hazelton
2007-09-03  9:47     ` David Schwartz
2007-09-03 17:43       ` Daniel Hazelton
2007-09-04  0:23         ` David Schwartz [this message]
2007-09-04  0:49           ` Daniel Hazelton
2007-09-04 15:10           ` Valdis.Kletnieks
2007-09-04 17:20             ` Daniel Hazelton
2007-09-03 17:18     ` Krzysztof Halasa
2007-09-03 18:11       ` Daniel Hazelton
2007-09-03 16:12 ` Valdis.Kletnieks
2007-09-04 15:01   ` Jarek Poplawski

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=MDEHLPKNGKAHNMBLJOLKOEGFGJAC.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=dhazelton@enter.net \
    --cc=espie@nerim.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®