From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC] Don't pass filename in multiboot command line
Date: Tue, 24 Nov 2009 12:48:22 +0100 [thread overview]
Message-ID: <20091124114822.GA32552@thorin> (raw)
In-Reply-To: <20091124113437.GA32380@thorin>
On Tue, Nov 24, 2009 at 12:34:37PM +0100, Robert Millan wrote:
>
> You're right. We should have documented this better. Perhaps by mentioning
> it in NEWS and in the release announcement. Sorry about that.
And in spite of that, both versions comply with the letter of the Multiboot
specification. Always keep in mind, when implementing a standard you must
follow the text and not the reference implementation. Never make any
assumptions about what an implementation can do other than what is
explicitly described in the text.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-11-24 11:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 13:23 [RFC] Don't pass filename in multiboot command line Vladimir 'phcoder' Serbinenko
2009-08-01 14:34 ` Robert Millan
2009-08-01 14:37 ` Vladimir 'phcoder' Serbinenko
2009-08-01 15:05 ` Robert Millan
2009-08-01 15:13 ` Vladimir 'phcoder' Serbinenko
2009-08-02 21:38 ` Robert Millan
2009-08-02 21:42 ` Vladimir 'phcoder' Serbinenko
2009-08-02 22:41 ` Robert Millan
2009-08-14 15:20 ` Vladimir 'phcoder' Serbinenko
2009-08-27 1:58 ` Seth Goldberg
2009-08-27 2:38 ` Seth Goldberg
2009-08-27 10:55 ` Michal Suchanek
2009-08-28 12:51 ` Robert Millan
2009-11-24 11:21 ` Thomas Schwinge
2009-11-24 11:34 ` Robert Millan
2009-11-24 11:48 ` Robert Millan [this message]
2009-11-24 13:02 ` Samuel Thibault
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=20091124114822.GA32552@thorin \
--to=rmh@aybabtu.com \
--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.