Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Scripting support (PATCH)
Date: Sun, 30 Oct 2005 10:45:14 +0100	[thread overview]
Message-ID: <874q6zl4np.fsf@student.han.nl> (raw)
In-Reply-To: <200510300625.22134.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sun, 30 Oct 2005 07:25:21 +0200")

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> Now, both Marco and Vladimir work on the scripting support separately, and I'm 
> glad to see the development going well. However, we must choose either of 
> them (or even none of them, if both are not good ;) to integrate a result 
> into the official code.
>
> I understand that there are two implementations because they do not agree on 
> one or more technical issues. As the maintainer, I need to listen to opinions 
> (not mental ones, but technical ones), and determine a direction. So I ask 
> you to speak pros and cons in both implementations (especially, Vladimir and 
> Marco). Even if you are not Vladimir or Marco, if you have any opinion, feel 
> free to describe it.

Right, I felt it hard to explain the direction I'd like to take on
this list.  So I have implemented the core functionality because that
definitely has to be right.

> - What are advantages in Vladimir's implementation?

More features.

> - What are disadvantages in Vladimir's implementation?

In my opinion it is not clean enough and does not integrate with GRUB
like I would like it to.  And Vladimir's patch was way too hard to
maintain when I started working on this a week ago.

> - What are advantages in Marco's implementation?

It's more flexible, cleaner and easier to maintain.

> - What are disadvantages in Marco's implementation?

It's work in progress.

> Here are my own:
>
> - What are advantages in Vladimir's implementation?
>
> It has already implemented most features we need.

Right, but I have asked Vladimir several times for a discussion on
this mailinglist about what the features are.  That discussion did not
properly take place yet.

> - What are disadvantages in Marco's implementation?
>
> Fewer features are implemented. The kernel is bloated.

What do you mean with the kernel is bloated?  My patch moves a lot of
responsibility to commands.  I would say it is less bloated.

Thanks,
Marco




  reply	other threads:[~2005-10-30  9:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 21:41 Scripting support (PATCH) Marco Gerards
2005-10-30  5:25 ` Yoshinori K. Okuji
2005-10-30  9:45   ` Marco Gerards [this message]
2005-10-30 11:55     ` Yoshinori K. Okuji
2005-10-30 12:17       ` Marco Gerards
2005-10-30 10:14   ` Marco Gerards
2005-10-30 14:41 ` Vladimir Serbinenko
2005-10-30 16:05   ` Marco Gerards
2005-10-30 16:46     ` Vladimir Serbinenko
2005-10-30 16:59       ` Marco Gerards
2005-10-30 17:15         ` Vladimir Serbinenko
2005-10-30 18:17           ` Marco Gerards
2005-10-31  6:39   ` Yoshinori K. Okuji
2005-10-30 20:49 ` Hollis Blanchard
2005-10-30 21:04   ` Marco Gerards
2005-10-31  6:45     ` Yoshinori K. Okuji
2005-10-31 18:58       ` Marco Gerards
2005-11-01 19:06         ` Marco Gerards
2005-11-01 19:55           ` Yoshinori K. Okuji
2005-11-03 21:58 ` Marco Gerards
2005-11-06 22:26   ` Marco Gerards
2005-11-08  3:38     ` Hollis Blanchard
2005-11-08 18:24       ` Marco Gerards
2005-11-09  6:14         ` Hollis Blanchard
     [not found] <200511010611.jA16B6Bq030884@dell01.dinaserver.com>
2005-11-02  9:37 ` adrian15
2005-11-06 22:13   ` Marco Gerards

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=874q6zl4np.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox