mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Perkel <mperkel@yahoo.com>
To: Glauber de Oliveira Costa <glommer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Instead of GPL License - Why not LKL? (Linux Kernel License)
Date: Fri, 15 Jun 2007 10:22:37 -0700 (PDT)	[thread overview]
Message-ID: <20070615172237.62204.qmail@web52502.mail.re2.yahoo.com> (raw)
In-Reply-To: <5d6222a80706142334m9f39383v20aff191f4501c50@mail.gmail.com>


--- 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.

Would it still be a problem if the licenses were
exactly the same?



       
____________________________________________________________________________________
Get the free Yahoo! toolbar and rest assured with the added security of spyware protection.
http://new.toolbar.yahoo.com/toolbar/features/norton/index.php

      parent reply	other threads:[~2007-06-15 17:22 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
2007-06-15  9:06       ` Jarek Poplawski
2007-06-15 17:28     ` Marc Perkel
2007-06-15 17:22   ` Marc Perkel [this message]

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=20070615172237.62204.qmail@web52502.mail.re2.yahoo.com \
    --to=mperkel@yahoo.com \
    --cc=glommer@gmail.com \
    --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®