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: [BUG] GRUBs option parsing needs fixing
Date: Sat, 10 Mar 2012 20:50:02 +0100	[thread overview]
Message-ID: <4F5BB06A.504@gmail.com> (raw)
In-Reply-To: <4F58D436.7040709@anvo-it.de>

On 08.03.2012 16:45, Andreas Vogel wrote:
>> Don't Reply or Reply-All to start a new thread. It messes up with
>> threading.
> Didn't i write that it was by accident??
No you didn't. You explicitly said that you used Reply-All to start a
new thread.
>  What else can i do other than
> to beg for pardon?
If I have something against you, it's your unwillingness to compromise.
With others it's easy to find compromise but with your approach "all or
nothing" it makes the whole thing much more stressful for both of us
without changing the final outcome. That's about basic rules of
communication and cooperation,
> C'mon, I'm talking about the GNU conventions/recommendations regarding
> argument parsing. I'm not talking about the GNU operating system, I
> thought I made it clear by even giving the link to that document.
> Without being able to parse '-xfoo' you will not be able to handle
> optional arguments in a consistent way. Because of this I disagree:
> "-xfoo" is necessary. You are right, "search -su UUID" demonstrates
> perfectly the weakness of the actual argument parsing. It's just buggy.
What is buggy and what isn't depends on what is considered correct. The
syntax "-s root" is widely used and is expected by many people. In fact
many people would consider it a bug if we don'r
> If nothing will be changed for short options, at least you need to
> mention in the manual that "search -s -u UUID" is OK but "search -u -s
> UUID" is NOT OK. And you need to mention that "search -su UUID" is OK
> but "search -us UUID" is NOT OK. I'm just mentioning the problems. If
> you or whoever decide that it's impossible to fix this (e.g. because
> of backward compatibility), that's another issue. Don't let's mix
> arguments for how smth should be and what the consequences will be. 
We're not in Platon's world of ideas. It's irrelevant how it should be.
At the end of the day there are only actions and consequences.

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



  reply	other threads:[~2012-03-10 19:50 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 [this message]
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         ` Ideas for the future Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:14           ` 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=4F5BB06A.504@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.