All of lore.kernel.org
 help / color / mirror / Atom feed
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:34:55 +0100	[thread overview]
Message-ID: <4F540A2F.1070008@gmail.com> (raw)
In-Reply-To: <4F5406C4.5030201@anvo-it.de>

On 05.03.2012 01:20, Andreas Vogel wrote:
> Am 05.03.2012 01:03, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>>> options? Any special reason?
>> 2) Why do you refuse to allow short options for all of the menuentry
>> Because it shares the space with options to menuentry.
> Don't understand what you mean. What is shared?
menuentry "title" hello {
    echo $1; sleep 10
}
>>> 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.
> Nice joke.... that code right now is a slippery slope... with all those
> obfuscated numbers. Just my 2 cents...
>
It may be unreadable and more difficult to maintain but neither matters 
much for the release. Readability cleanup can be done after release 
without problems.
If we start clean this and other files now, we'll spend too much time 
and be generally counterproductive.
I understand that it may feel as if I'm having anything against you but 
I don't, just releasing 2.00 is now a top priority and because of this 
fixing bugs is important. Everything that is not to fix bugs or was 
already announced at freeze as still accepted (all of which is now in) 
is secondary now.
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2012-03-05  0:35 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
2012-03-05  0:20     ` Andreas Vogel
2012-03-05  0:34       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4F540A2F.1070008@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.