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: Device instability, gettext and default
Date: Mon, 05 Mar 2012 01:03:57 +0100 [thread overview]
Message-ID: <4F5402ED.6010707@gmail.com> (raw)
In-Reply-To: <4F53FFE7.2060407@anvo-it.de>
On 05.03.2012 00:51, Andreas Vogel wrote:
> Am 03.03.2012 14:37, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> === modified file 'grub-core/commands/menuentry.c'
>> --- grub-core/commands/menuentry.c 2012-02-26 16:28:05 +0000
>> +++ grub-core/commands/menuentry.c 2012-03-03 12:11:30 +0000
>> @@ -36,6 +36,8 @@
>> N_("Keyboard key to quickly boot this entry."), N_("KEYBOARD_KEY"), ARG_TYPE_STRING},
>> {"source", 4, 0,
>> N_("Use STRING as menu entry body."), N_("STRING"), ARG_TYPE_STRING},
>> + {"id", 1, GRUB_ARG_OPTION_REPEATABLE,
>> + N_("Menu entry identifier."), N_("STRING"), ARG_TYPE_STRING},
>> {0, 0, 0, 0, 0, 0}
>> };
> 1) After bzr-pulling your latest changes and reviewing that source
> again, i noticed that you are using GRUB_ARG_OPTION_REPEATABLE for the
> new id option but you are not handling multiple ids (as far as i can see).
It wasn't intentional. Fixed now.
> 2) Why do you refuse to allow short options for all of the menuentry
> options? Any special reason?
Because it shares the space with options to menuentry.
> 3) Wouldn't it be a good chance to use my patch which uses an anonymous
> enum for indexing the options array?
No. Thinking like this is a slippery slope. Such patches may also
contain bugs (if you confuse 2 numbers).
Your patch could be committed into experimental but not trunk.
Life doesn't end at 2.00.
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-03-05 0:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 13:37 Device instability, gettext and default Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 14:27 ` Jordi Mallach
2012-03-03 14:51 ` Andreas Vogel
2012-03-03 15:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 19:48 ` Andreas Vogel
2012-03-03 20:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 20:08 ` Andreas Vogel
2012-03-03 20:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-04 23:51 ` Andreas Vogel
2012-03-05 0:03 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-03-05 0:20 ` Andreas Vogel
2012-03-05 0:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 11:51 ` Andreas Vogel
2012-03-05 12:37 ` 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=4F5402ED.6010707@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.