mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "debian developer" <debiandev@gmail.com>
To: "Kevin Bowling" <lkml@kev009.com>
Cc: "Glauber de Oliveira Costa" <glommer@gmail.com>,
	"Marc Perkel" <mperkel@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Instead of GPL License - Why not LKL? (Linux Kernel License)
Date: Fri, 15 Jun 2007 12:22:10 +0530	[thread overview]
Message-ID: <f24d23310706142352m569739e2x23f705f7a1b33ee@mail.gmail.com> (raw)
In-Reply-To: <11f674920706142347t297dc6e7w82486c9787195f08@mail.gmail.com>

On 6/15/07, Kevin Bowling <lkml@kev009.com> wrote:
> On 6/14/07, Glauber de Oliveira Costa <glommer@gmail.com> wrote:
> > On 6/15/07, Marc Perkel <mperkel@yahoo.com> wrote:
> > > I've been somewhat following the GPL2 vs. GPL3 debate
> > > and the problem is that it leads to confusion. GPL3 is
> > > nothing like GPL2 and the GPLx leads people to believe
> > > that GPL3 is just GPL3 improved.
> > >
> > > So - just throwing out the idea that if Linus is
> > > unhappy with GPL3 that Linux lose the GPLx license and
> > > call it the Linux Kernel License or LKL for short. So
> > > LKL could equal GPL2.
> >
> > It seems it would require agreement by all copyright holders, much
> > like the v2->v3 transition would do. If it makes the 2->3 transition
> > unfeasible, the same may apply here.
>
> If I'm not mistaken, the OP is suggesting that the name simply be
> changed from GPL to LKL to avoid confusion of GPL2 vs GPL3.  Same
> verbiage, different name.  If these FSF loonies keep cutting into our
> corner of pragmatism, I am inclined to agree :-).

Even if it's just a name change, it will be a different license and requires the
agreement of all authors. It's much easier( not that we want to) to go
to GPLv3 than
go to LKL.

  reply	other threads:[~2007-06-15  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15  6:21 Marc Perkel
2007-06-15  6:34 ` Glauber de Oliveira Costa
2007-06-15  6:47   ` Kevin Bowling
2007-06-15  6:52     ` debian developer [this message]
2007-06-15  9:06       ` Jarek Poplawski
2007-06-15 17:28     ` Marc Perkel
2007-06-15 17:22   ` Marc Perkel

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=f24d23310706142352m569739e2x23f705f7a1b33ee@mail.gmail.com \
    --to=debiandev@gmail.com \
    --cc=glommer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kev009.com \
    --cc=mperkel@yahoo.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

all inboxes | Powered by JetHome®