From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: a bug in read
Date: Wed, 09 Jul 2008 20:05:06 +0300 [thread overview]
Message-ID: <4874EFC2.7020504@nic.fi> (raw)
In-Reply-To: <1215584072.31230.9.camel@dv>
Pavel Roskin wrote:
> By the way, read is not a part of grub-emu. We'll need to improve the
> build system to make such oversights less likely. We also need "exit"
> in grub-emu, as "reboot" doesn't sound right.
I think there should be emu arch that provides architecture specific
functionality. This way we use exactly same code paths for everything.
Then we can catch bugs more easily.
next prev parent reply other threads:[~2008-07-09 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 22:18 a bug in read Yoshinori K. Okuji
2008-07-09 6:14 ` Pavel Roskin
2008-07-09 17:05 ` Vesa Jääskeläinen [this message]
2008-07-09 17:56 ` Javier Martín
2008-07-11 18:23 ` Pavel Roskin
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=4874EFC2.7020504@nic.fi \
--to=chaac@nic.fi \
--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.