All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] memdisk plus lnxboot extension
Date: Wed, 23 Jan 2008 09:54:33 +0100	[thread overview]
Message-ID: <873asoudkm.fsf@xs4all.nl> (raw)
In-Reply-To: <20080122135757.GA11484@thorin> (Robert Millan's message of "Tue,  22 Jan 2008 14:57:57 +0100")

Robert Millan <rmh@aybabtu.com> writes:

>> 2. Easy to modify
>> users may not know how to create core.img, but modifying files in a,
>> say, tar or cpio archive is very easy. They can do simple tasks like
>> replacing splash image without too much knowledge of grub2.
>>
>> 3. Multiple configuration
>> We can use the same core.img, but different initrd to start grub2 with
>> different configuration.
>
> I don't think these two make a big difference, but well.
>
> No objection from me, then.

Personally I do not want to add every feature everyone comes up with,
just because there is a patch.

When is this feature useful?  Can you give an example?  More features
can mean more bugs, more maintainance work, etc.  If the feature is
not worthwhile for more than one person, I am not sure if it should be
included.  Perhaps a better explaination of the problem to solve,
instead of what the patch does might help here.

--
Marco





  parent reply	other threads:[~2008-01-23  8:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29  9:05 [PATCH] memdisk plus lnxboot extension Bean
2007-12-30 13:48 ` Robert Millan
2008-01-20 23:24   ` Robert Millan
2008-01-22  4:25     ` Bean
2008-01-22 13:57       ` Robert Millan
2008-01-22 16:22         ` Bean
2008-01-22 16:51           ` Robert Millan
2008-01-22 17:17             ` Bean
2008-01-22 19:53               ` Robert Millan
2008-01-23  8:54         ` Marco Gerards [this message]
2008-01-23 16:18           ` Bean
2008-01-23 19:01             ` Bean
2008-01-23 19:14               ` Robert Millan
2008-01-23 19:24                 ` Bean
2008-01-23 20:15                   ` Robert Millan
2008-01-23 21:04                     ` Bean
2008-01-23 21:15                       ` Robert Millan
2008-01-24  3:40                         ` Bean
2008-01-24 11:32                           ` Robert Millan
2008-01-24 11:49                             ` Bean
2008-01-24 14:25                               ` Robert Millan
2008-01-24 14:57                                 ` Bean
2008-01-24 15:16                                   ` Robert Millan
2008-01-24 16:55                                 ` Robert Millan
2008-01-24 17:04                                   ` Bean
2008-01-24 17:21                                     ` Robert Millan
2008-01-24 18:06                                       ` Marco Gerards
2008-01-24 21:23                               ` Yoshinori K. Okuji
2008-01-23 19:10             ` Robert Millan
2008-01-23  8:48       ` 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=873asoudkm.fsf@xs4all.nl \
    --to=mgerards@xs4all.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 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.