From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] split floppy support off biosdisk
Date: Thu, 19 Jun 2008 00:15:02 +0200 [thread overview]
Message-ID: <20080618221502.GA24751@thorin> (raw)
In-Reply-To: <200806181952.27260.okuji@enbug.org>
On Wed, Jun 18, 2008 at 07:52:26PM +0200, Yoshinori K. Okuji wrote:
> On Tuesday 17 June 2008 14:54:23 Robert Millan wrote:
> > On Tue, Jun 17, 2008 at 02:33:48PM +0200, Robert Millan wrote:
> > > On Tue, Jun 17, 2008 at 02:22:15PM +0200, Robert Millan wrote:
> > > > A problem I see here is that LZMA is licensed under GPLv2-only, so it'd
> > > > probably take a rewrite of the decompressor for us to use it, or ask
> > > > the author to make it "or later".
> > > >
> > > > By the looks (no explicit license header in individual files) I doubt
> > > > it was an explicit decision to exclude GPLv3. I'll try contact him.
> > >
> > > Actually, after checking:
> > >
> > > http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
> > >
> > > it seems there's no problem. But I'd like to see what Okuji thinks about
> > > it.
> >
> > CCing him.
>
> Which implementation of LZMA do you refer to? I think LZMA SDK is available
> under LGPL, and most of LZMA Utils is also under LGPL. So there should be no
> problem.
I expected that LGPL 2.1 wouldn't be compatible with GPL 3, but it seems
that it is; so unless I missed something there's no problem at all.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-06-18 22:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 17:48 [RFC] split floppy support off biosdisk Robert Millan
2008-06-16 0:32 ` Pavel Roskin
2008-06-16 6:30 ` Bean
2008-06-16 9:15 ` Robert Millan
2008-06-16 11:03 ` Bean
2008-06-16 11:20 ` Javier Martín
2008-06-16 11:47 ` Bean
2008-06-16 12:09 ` Javier Martín
2008-06-16 12:37 ` Bean
2008-06-16 21:31 ` Robert Millan
2008-06-17 2:03 ` Bean
2008-06-17 2:47 ` Javier Martín
2008-06-17 3:06 ` Bean
2008-06-17 14:39 ` Javier Martín
2008-06-17 14:52 ` Bean
2008-06-17 17:23 ` Javier Martín
2008-06-17 17:35 ` Bean
2008-06-18 3:14 ` Javier Martín
2008-06-18 3:49 ` Pavel Roskin
2008-06-18 6:55 ` Bean
2008-06-18 7:36 ` Pavel Roskin
2008-06-18 8:01 ` Bean
2008-06-18 11:29 ` Bean
2008-06-18 17:37 ` Robert Millan
2008-06-18 11:40 ` Javier Martín
2008-06-18 13:12 ` Bean
2008-06-18 13:28 ` Bean
2008-06-18 13:33 ` Javier Martín
2008-06-18 17:32 ` Isaac Dupree
2008-06-18 17:38 ` Robert Millan
2008-06-18 3:48 ` Javier Martín
2008-06-17 15:02 ` Bean
2008-06-17 15:54 ` Pavel Roskin
2008-06-18 17:53 ` Yoshinori K. Okuji
2008-06-17 12:22 ` Robert Millan
2008-06-17 12:33 ` Robert Millan
2008-06-17 12:54 ` Robert Millan
2008-06-18 17:52 ` Yoshinori K. Okuji
2008-06-18 22:15 ` Robert Millan [this message]
2008-06-18 23:56 ` Pavel Roskin
2008-06-19 2:14 ` Yoshinori K. Okuji
2008-06-19 2:37 ` Pavel Roskin
2008-06-19 12:20 ` Robert Millan
2008-06-19 19:22 ` Pavel Roskin
2008-06-16 13:06 ` Pavel Roskin
2008-06-16 14:06 ` Bean
2008-06-16 14:38 ` Pavel Roskin
2008-06-16 21:13 ` Robert Millan
2008-06-16 21:12 ` 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=20080618221502.GA24751@thorin \
--to=rmh@aybabtu.com \
--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.