From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Roadmap for LUA support in GRUB
Date: Fri, 13 Nov 2009 21:54:48 +0100 [thread overview]
Message-ID: <20091113205448.GA12722@thorin> (raw)
In-Reply-To: <ca0f59980911131134x4ff1d1a4qb625d8431afc428c@mail.gmail.com>
On Sat, Nov 14, 2009 at 03:34:27AM +0800, Bean wrote:
>
> Hi,
>
> As I see it, one problem of grub-extra is that it can't be compiled
> separately, so user have to setup an environment to build it,
Why? Modules from grub-extras can be compiled in-tree just as fine.
> And as they have two revision system, this make
> it difficult to track previous bug.
I've been looking into migrating grub-extras to Bazaar, but haven't found
the time. Would it help if I do this?
> And it's also the question of confidence, I don't see anyone
> claim responsibility for grub-extra, it' more like a garbage dump to
> me. It's hard to convince others to send patches on something that's
> not actively maintained.
I think you're presenting the problem in a way that can't have any possible
solution:
- I made an open offer to anyone who would want to maintain LUA in
grub-extras. You weren't interested.
- Now you say that you made a fork of GRUB because LUA in grub-extras
isn't being properly maintained.
I'm afraid I can't help you there. If you have other reasons for this, feel
free to explain them, and maybe we can find a solution.
--
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-11-13 20:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 3:38 Roadmap for LUA support in GRUB Roman Shaposhnik
2009-11-11 10:41 ` Felix Zielcke
2009-11-11 18:13 ` Roman Shaposhnik
2009-11-11 18:53 ` Vladimir 'phcoder' Serbinenko
2009-11-12 2:46 ` Roman Shaposhnik
2009-11-11 19:01 ` Felix Zielcke
2009-11-12 10:38 ` Robert Millan
2009-11-13 8:08 ` Roman Shaposhnik
2009-11-13 9:46 ` Felix Zielcke
2009-11-13 11:54 ` Vladimir 'phcoder' Serbinenko
2009-11-13 15:34 ` Roman Shaposhnik
2009-11-13 18:12 ` Bean
2009-11-13 18:29 ` Roman Shaposhnik
2009-11-13 19:06 ` Robert Millan
2009-11-13 19:34 ` Bean
2009-11-13 20:22 ` Vladimir 'phcoder' Serbinenko
2009-11-14 8:11 ` Bean
2009-11-14 12:29 ` Vladimir 'phcoder' Serbinenko
2009-11-13 20:54 ` Robert Millan [this message]
2009-12-29 4:24 ` Bruce O. Benson
[not found] ` <20100101114244.GE3692@thorin>
2010-01-02 7:35 ` Bruce O. Benson
2009-11-13 11:56 ` 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=20091113205448.GA12722@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.