From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.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:22:03 +0100 [thread overview]
Message-ID: <4AFDBFEB.6060702@gmail.com> (raw)
In-Reply-To: <ca0f59980911131134x4ff1d1a4qb625d8431afc428c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Bean wrote:
> On Sat, Nov 14, 2009 at 3:06 AM, Robert Millan <rmh@aybabtu.com> wrote:
>
>> On Sat, Nov 14, 2009 at 02:12:38AM +0800, Bean wrote:
>>
>>> But no worry, I've created a fork project BURG that contains some
>>> brand-new features, the LUA engine will be added back soon.
>>>
>> Does that make it any easier than maintaining LUA in grub-extras?
>>
>> When moving it there, I made it clear [1] that anyone who wishes to work
>> on LUA is welcome to use the grub-extras repository for that purpose [1].
>>
>> I expected a reply from you, but there was none.
>>
>> [1] http://lists.gnu.org/archive/html/grub-devel/2009-09/msg00424.html
>>
>
> 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, which is
> not straightforward.
Then propose a better system. I don't find any problem with setting
GRUB_CONTRIB
> And as they have two revision system, this make
> it difficult to track previous bug. For example, it's hard to tell
> which revision of grub-extra can compile with which main stream
> revision.
It's always latest-to-latest. And it's how it's done in Debian.
> 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.
>
The same code wouldn't have recieved more attention if it was in the
mainline.
You can pretty much say nobody looks into hello/hello.c but is it a
reason to tell it garbage.
I personally handle grub-extras the same way as GRUB2
Actually the same people that take care of mainline also take care of
grub-extras. I also have two new things on the queue for grub-extras:
LUKS and gPXE import.
--
Regards
Vladimir 'phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2009-11-13 20:22 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 [this message]
2009-11-14 8:11 ` Bean
2009-11-14 12:29 ` Vladimir 'phcoder' Serbinenko
2009-11-13 20:54 ` Robert Millan
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=4AFDBFEB.6060702@gmail.com \
--to=phcoder@gmail.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.