All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Reinauer <stepan@coresystems.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GPL version 3
Date: Thu, 5 Jul 2007 00:58:42 +0200	[thread overview]
Message-ID: <20070704225842.GB32653@coresystems.de> (raw)
In-Reply-To: <87bqerkh8x.wl@dekkers.cx>

* Jeroen Dekkers <jeroen@vrijschrift.org> [070704 23:10]:
> At Wed, 4 Jul 2007 21:40:15 +0200,
> Yoshinori K. Okuji wrote:
> > So I bet that GRUB Legacy should remain under GPLv2. But this can cause some 
> > problem potentially. Let's say, we find the same bug both in GRUB Legacy and 
> > in GRUB 2. In the current trend, the bug would be fixed in GRUB 2 sooner. But 
> > this fix may not be backported to GRUB Legacy as it is, once GRUB 2 migrates 
> > to GPLv3, because of the license incompatibility. Thus this means that the 
> > maintenance of GRUB Legacy would be harder.

These sound very much like house made problems, invented to push a
conversion to GPL3. Why would it be any harder to maintain Grub legacy?

1. There is no shared code between GRUB2 and Grub Legacy

2. Just have all the patches GPLv2 or later, and it will automatically
   be GPLv3 or GPLv2, whatever applies. 

> Are you sure about this? Given that we've assigned copyright to the
> FSF, the FSF can decide under which free software license to license
> that code. So I don't really see why we can't release the same code
> under GPLv2 or later in GRUB Legacy and under GPLv3 or later in GRUB2.
 
Yes, it is simply not the author's choice anymore, but the FSF's. At
least in some countries of the world.

Stefan

-- 
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
      Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: info@coresystems.de  • http://www.coresystems.de/



  reply	other threads:[~2007-07-04 22:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 19:40 GPL version 3 Yoshinori K. Okuji
2007-07-04 20:23 ` Alex Roman
2007-07-04 21:09 ` Thomas Schwinge
2007-07-04 21:10 ` Jeroen Dekkers
2007-07-04 22:58   ` Stefan Reinauer [this message]
2007-07-07 19:01     ` Robert Millan
2007-07-04 23:06   ` Stefan Reinauer
2007-07-04 23:34     ` Jeroen Dekkers
2007-07-07 19:03   ` Robert Millan
2007-07-04 21:53 ` Jerone Young
2007-07-04 22:53 ` Stefan Reinauer
2007-07-05  5:47 ` Marco Gerards
2007-07-07 19:06 ` Robert Millan
2007-07-08 16:10   ` Robert Millan
2007-07-14 13:02 ` Yoshinori K. Okuji
2007-07-21 23:38   ` Yoshinori K. Okuji
2007-07-22  0:35     ` Alex Roman
2007-07-22 13:45       ` Marco Gerards
2007-07-22  8:04     ` Robert Millan
2007-07-22 13:56       ` Thomas Schwinge
2007-07-22 14:43         ` grub 1.96 (Re: GPL version 3) Robert Millan

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=20070704225842.GB32653@coresystems.de \
    --to=stepan@coresystems.de \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.