From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu vl.c vl.h hw/an5206.c hw/etraxfs.c hw/inte...
Date: Wed, 31 Oct 2007 03:21:00 +0100 [thread overview]
Message-ID: <1193797260.16781.380.camel@rapid> (raw)
In-Reply-To: <E1In2mT-0000lo-2D@cvs.savannah.gnu.org>
On Wed, 2007-10-31 at 01:54 +0000, Andrzej Zaborowski wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Andrzej Zaborowski <balrog> 07/10/31 01:54:05
>
> Modified files:
> . : vl.c vl.h
> hw : an5206.c etraxfs.c integratorcp.c mcf5208.c
> mips_malta.c mips_mipssim.c mips_pica61.c
> mips_r4k.c palm.c pc.c ppc405_boards.c
> ppc_chrp.c ppc_oldworld.c ppc_prep.c r2d.c
> realview.c shix.c spitz.c sun4m.c sun4u.c
> versatilepb.c
>
> Log message:
> Set boot sequence from command line (Dan Kenigsberg).
There have been remarks about this patch that have not been addressed
(not even answered, in fact). For example, the MAX_BOOT_DEVICES is set
to 3 when more than 3 boot devices are possible to select (see the
BOOTCHARS definition), which clearly shows the patch is not consistent.
Furthermore, the patch breaks the coding style in some files (at least
the ones I checked), which is weird.
Seems _very_ strange to see it commited, then.
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-31 2:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 1:54 [Qemu-devel] qemu vl.c vl.h hw/an5206.c hw/etraxfs.c hw/inte Andrzej Zaborowski
2007-10-31 2:21 ` J. Mayer [this message]
2007-10-31 2:35 ` andrzej zaborowski
2007-10-31 4:42 ` J. Mayer
2007-10-31 10:01 ` andrzej zaborowski
2007-10-31 10:22 ` J. Mayer
2007-10-31 22:49 ` J. Mayer
2007-11-01 0:01 ` andrzej zaborowski
2007-11-01 19:12 ` J. Mayer
2007-11-03 0:01 ` andrzej zaborowski
2007-11-03 0:21 ` J. Mayer
2007-11-03 1:18 ` Thiemo Seufer
2007-11-03 12:40 ` J. Mayer
2007-11-05 13:04 ` [Qemu-devel] multiple boot devices J. Mayer
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=1193797260.16781.380.camel@rapid \
--to=l_indien@magic.fr \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).