From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Support FreeBSD in osdetect.lua
Date: Wed, 22 Jul 2009 19:51:08 +0200 [thread overview]
Message-ID: <20090722175108.GM8706@thorin> (raw)
In-Reply-To: <d7ead6de0907211450ma824fe7u8669e1db0dadb170@mail.gmail.com>
On Tue, Jul 21, 2009 at 11:50:12PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >
> > Obviously, the zfs part shouldn't go in yet.
> >
> We discussed with Robert Millan the issue and decided that zfs.mod
> will go to grub-extras. Just I had no time to upload it yet. As zfs
> part of osdetect.lua is harmless and effectless if no zfs.mod is
> present I see no reason for it not to be in mainstream
Well, this gets a bit more complicated. grub-extras is not part of GNU GRUB,
but osdetect.lua is (currently). I'm not sure if we should make GRUB
components depend on grub-extras this way (I think this is Pavel's point).
I think we should contemplate to put LUA scripting in grub-extras too. Like
other components of grub-extras, we don't have copyright assignment for it,
so it would fit well the purpose of grub-extras. This would render the
question about zfs moot.
--
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-07-22 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 13:45 [PATCH] Support FreeBSD in osdetect.lua Vladimir 'phcoder' Serbinenko
2009-07-21 16:02 ` Pavel Roskin
2009-07-21 20:17 ` Vladimir 'phcoder' Serbinenko
2009-07-21 21:25 ` Pavel Roskin
2009-07-21 21:50 ` Vladimir 'phcoder' Serbinenko
2009-07-22 17:51 ` Robert Millan [this message]
2009-07-22 18:02 ` Vladimir 'phcoder' Serbinenko
2009-07-25 16:10 ` Robert Millan
2009-07-25 16:46 ` Vladimir 'phcoder' Serbinenko
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=20090722175108.GM8706@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.