From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: "Michel Dänzer" <michel@daenzer.net>
Subject: Re: hfs patch (Re: State of GRUB on PowerPC)
Date: Sat, 21 Feb 2009 13:46:16 +0100 [thread overview]
Message-ID: <20090221124615.GA16068@thorin> (raw)
In-Reply-To: <20090210105018.GA16255@nubol.oskuro.net>
On Tue, Feb 10, 2009 at 11:50:18AM +0100, Jordi Mallach wrote:
> On Tue, Feb 10, 2009 at 10:54:55AM +0100, Michel Dänzer wrote:
> > > > Could you be more specific about what the table contents mean?
> > BTW, let me point out again that this table including comment is a
> > verbatim copy from the Linux kernel fs/hfs/string.c . Sorry if I didn't
> > make this clear enough in my original post.
>
> Ugh, welcome our GPLv3 party. v2 members not invited. :/
Just to make it clear: I haven't said there's a problem with license
compatibility. There *might* be, depending on the exact meaning of those
bytes, but it's unlikely.
--
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."
next prev parent reply other threads:[~2009-02-21 12:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 7:19 State of GRUB on PowerPC Michel Dänzer
2009-01-27 16:54 ` Vesa Jääskeläinen
2009-01-27 17:15 ` Michel Dänzer
2009-01-29 2:57 ` Pavel Roskin
2009-01-29 16:18 ` Michel Dänzer
2009-02-07 19:48 ` hfs patch (Re: State of GRUB on PowerPC) Robert Millan
2009-02-08 4:38 ` Pavel Roskin
2009-02-09 14:19 ` Robert Millan
2009-02-10 9:55 ` Michel Dänzer
2009-02-10 9:54 ` Michel Dänzer
2009-02-10 10:50 ` Jordi Mallach
2009-02-10 12:06 ` Jordi Mallach
2009-02-10 12:12 ` Michel Dänzer
2009-02-21 12:46 ` Robert Millan [this message]
2009-02-10 14:47 ` Robert Millan
2009-02-11 9:24 ` Michel Dänzer
2009-02-21 13:01 ` 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=20090221124615.GA16068@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=michel@daenzer.net \
/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.