public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Colin Watson <cjwatson@ubuntu.com>,
	Bron Gondwana <brong@fastmail.fm>,
	Ric Wheeler <rwheeler@redhat.com>,
	The development of BTRFS <linux-btrfs@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: grub-0.97: btrfs multidevice support [PATCH]
Date: Sun, 27 Sep 2009 12:18:04 +0200	[thread overview]
Message-ID: <20090927101804.GA22642@thorin> (raw)
In-Reply-To: <6149e97b0909262029w30fe3adcq591515f0f2b156c4@mail.gmail.com>

On Sun, Sep 27, 2009 at 11:29:11AM +0800, Peng Tao wrote:
> >
> > It would be great if somebody could take up Edward's work and port it to
> > GRUB 2. If nobody else does then I'd be interested in doing so myself,
> > although I will not be able to start for a month or two from now.
> Is there any guild lines for porting GPLv2 code to GRUB2? I've looked
> at the GRUB2 wiki but very few things are documented there
> (http://grub.enbug.org/). I'd like to see what it would take to port
> the patches. If I can afford it, I'd like to try.

I assume you mean GPLv2-only code (as opposed to GPLv2-or-later). First
step would be to contact the copyright holders and ask them to relicense
under v3-compatible terms (e.g. GPLv2-or-later).  Chances are they didn't
chose these terms as an act of hostility, but were simply being zealous
about allowing something before they knew what it is.

If that doesn't work, we'll always have Par^W clean room
(http://en.wikipedia.org/wiki/Clean_room_design).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

  reply	other threads:[~2009-09-27 10:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 19:01 grub-0.97: btrfs multidevice support [PATCH] Edward Shishkin
2009-09-24 20:21 ` Robert Millan
2009-09-24 22:38   ` Bron Gondwana
2009-09-25 14:09     ` Robert Millan
2009-09-25 14:16       ` Ric Wheeler
2009-09-25 15:22         ` Robert Millan
2009-09-25 15:01       ` Colin Watson
2009-09-25 23:35         ` Joel Becker
2009-09-25 23:47         ` Bron Gondwana
2009-09-27  3:29         ` Peng Tao
2009-09-27 10:18           ` Robert Millan [this message]
2009-09-28  1:53             ` Peng Tao
2009-09-28  7:47               ` Vladimir 'phcoder' Serbinenko
2009-09-28 15:36                 ` Chris Mason
2009-10-02 20:48                 ` Robert Millan
2009-09-27 10:38     ` 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=20090927101804.GA22642@thorin \
    --to=rmh@aybabtu.com \
    --cc=brong@fastmail.fm \
    --cc=chris.mason@oracle.com \
    --cc=cjwatson@ubuntu.com \
    --cc=grub-devel@gnu.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rwheeler@redhat.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