From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Andreas Vogel <Andreas.Vogel@anvo-it.de>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Ideas for the future
Date: Thu, 08 Mar 2012 15:11:46 +0100 [thread overview]
Message-ID: <4F58BE22.1020003@gmail.com> (raw)
In-Reply-To: <4F54DF19.7000804@anvo-it.de>
On 05.03.2012 16:43, Andreas Vogel wrote:
> Am 05.03.2012 13:54, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>>> option with an optional argument. By this we would have had what you
>>> preference and my way too. Regarding optional arguments the option
>>> handling in GRUB is actually broken by design, so this is,
>>> unfortunately, not an option.
>> When i implemented my patches, i wanted to use both ways: a command line
>> Again it's unfortunate that noone noticed it when it was committed and
>> now we're stuck with it.
> You should think about that again. GRUB is broken regarding that and it
> should be fixed anyway. Right now it seems that there is only one
> command which uses GRUB_ARG_OPTION_OPTIONAL so maybe it's one of the
> last chances to have a cheap fix.
Learn to use rgrep before making unsupported, easy to check claims:
./grub-core/commands/search_wrap.c: {"set", 's',
GRUB_ARG_OPTION_OPTIONAL,
./grub-core/loader/i386/bsd.c: {"serial", 'h', GRUB_ARG_OPTION_OPTIONAL,
./grub-core/loader/i386/bsd.c: {"serial", 'h', GRUB_ARG_OPTION_OPTIONAL,
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-03-08 14:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 1:13 Ideas for the future Andreas Vogel
2012-03-05 1:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 1:35 ` Samuel Thibault
2012-03-05 1:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 9:23 ` Samuel Thibault
2012-03-05 11:16 ` Andreas Vogel
2012-03-05 12:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 15:43 ` Andreas Vogel
2012-03-08 13:12 ` [BUG] GRUBs option parsing needs fixing Andreas Vogel
2012-03-08 14:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 14:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:03 ` Andreas Vogel
2012-03-08 15:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:28 ` Lennart Sorensen
2012-03-08 15:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 16:11 ` Andreas Vogel
2012-03-08 15:45 ` Andreas Vogel
2012-03-10 19:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 0:08 ` Andreas Vogel
2012-03-11 1:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 1:59 ` Andreas Vogel
2012-03-11 2:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:25 ` Lennart Sorensen
2012-03-08 15:58 ` Andreas Vogel
2012-03-08 15:24 ` Lennart Sorensen
2012-03-08 14:11 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-03-08 15:14 ` Ideas for the future Andreas Vogel
2012-03-08 15:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 16:33 ` Andreas Vogel
2012-03-08 14:23 ` Vladimir 'φ-coder/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=4F58BE22.1020003@gmail.com \
--to=phcoder@gmail.com \
--cc=Andreas.Vogel@anvo-it.de \
--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.