From: Andreas Vogel <Andreas.Vogel@anvo-it.de>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [BUG] GRUBs option parsing needs fixing
Date: Thu, 08 Mar 2012 16:03:17 +0100 [thread overview]
Message-ID: <4F58CA35.2060506@anvo-it.de> (raw)
In-Reply-To: <4F58C2E7.6080000@gmail.com>
Am 08.03.2012 15:32, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
> On 08.03.2012 15:15, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 08.03.2012 14:12, Andreas Vogel wrote:
>>> Hi all,
>>>
>>> I start a new thread with this mail in order to have a thread on its
>>> own
>>> for this subject.
>> Please don't CC Colin Watson (or me for that matter) for everything,
>> it's bad tone.
I just used Reply-All in my mail program, so please excuse me and I
really hope that i didn't offend anyone, it was not by purpose.
>>> In another thread we've already had some discussion about GRUBs option
>>> parsing. I wanna summarize and describe here about the issue.
>>>
>>> Right now I see 2 problems with GRUBs argument parsing:
>>>
>>> 1) GRUBs argument parsing is not POSIX compliant.
>> We don't follow POSIX.
But you were telling that you follow GNU, right? And regarding this
subject GNU follows POSIX, qed.
next prev parent reply other threads:[~2012-03-08 15:03 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 [this message]
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 ` 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=4F58CA35.2060506@anvo-it.de \
--to=andreas.vogel@anvo-it.de \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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.