qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Updated BGR vs. RGB vga patch...
Date: Mon, 10 Apr 2006 17:59:33 +0100	[thread overview]
Message-ID: <200604101759.34399.paul@codesourcery.com> (raw)
In-Reply-To: <443A8D0C.4030807@win4lin.com>

On Monday 10 April 2006 17:51, Leonardo E. Reiter wrote:
> I was talking about enabling the use of the -bgr flag at compile time,
> to save the check at runtime if the user doesn't even care about the
> flag, not forcing the determination of the blit order altogether at
> compile-time.  In any case, this is moot, your clarification on how to
> better implement it makes it much more clear to me and is a much better
> idea.  Mails to the list are a bit delayed, that's all ;)

Ok. For the record I also think it's a bad idea to have features conditionally 
compiled. Either something is worth including, or we have to ask whether 
there's any point having it in qemu at all.
The exception being debug code, which probably isn't useful unless you're 
already building qemu from source.

Paul

  reply	other threads:[~2006-04-10 16:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 16:25 [Qemu-devel] Updated BGR vs. RGB vga patch Leonardo E. Reiter
2006-04-10 16:35 ` Paul Brook
2006-04-10 16:41   ` Leonardo E. Reiter
2006-04-10 16:46     ` Paul Brook
2006-04-10 16:48       ` Leonardo E. Reiter
2006-04-10 16:44   ` Leonardo E. Reiter
2006-04-10 16:49     ` Paul Brook
2006-04-10 16:51       ` Leonardo E. Reiter
2006-04-10 16:59         ` Paul Brook [this message]
2006-04-10 18:24           ` Leonardo E. Reiter
2006-04-10 19:08             ` malc
2006-04-10 19:11               ` Leonardo E. Reiter
2006-04-11 17:06               ` Leonardo E. Reiter
2006-04-11 17:11               ` Leonardo E. Reiter
2006-04-10 18:25           ` Leonardo E. Reiter
2006-04-10 23:12 ` Thiemo Seufer
2006-04-10 23:22   ` Leonardo E. Reiter

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=200604101759.34399.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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).