From: Glauber Costa <glommer@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: glommer@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: start qemu failed with --enable-kvm -vga std
Date: Wed, 8 Apr 2009 15:07:20 -0300 [thread overview]
Message-ID: <5d6222a80904081107t55accbdag1d4621726cd3ba2c@mail.gmail.com> (raw)
In-Reply-To: <200904081847.07083.paul@codesourcery.com>
On Wed, Apr 8, 2009 at 2:47 PM, Paul Brook <paul@codesourcery.com> wrote:
> On Wednesday 08 April 2009, M. Warner Losh wrote:
>> In message: <5d6222a80904081025j1644b6bay17d1ff942247971@mail.gmail.com>
>>
>> Glauber Costa <glommer@gmail.com> writes:
>> : In all seriousness, no matter how good your series for improving kvm
>> : registration
>> : are, it is unlikely to hit the stable branch. So I believe a good deal
>> : would have something
>> : on the line of this patch applied to stable, leaving unstable as is,
>> : until we can find a better
>> : solution.
>>
>> Huh? It is unlikely to be merged into stable, so let's commit it to
>> stable?
>
> I think the suggestion is that we apply an ugly hack on just the stable
> branch, and fix it properly later on the development.
>
> FWIW I think this is a bad idea. We should never fix something on the stable
> branch that isn't also fixed on the development branch. If the changes are
> causing problems, then my suggestion is to revert the original change (i.e.
> the support for >64k roms).
Just checked, and the > 64 roms patch is not on stable branch.
So this is a non issue.
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2009-04-08 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 3:11 [Qemu-devel] start qemu failed with --enable-kvm -vga std Peng Huang
2009-04-08 12:27 ` Paul Brook
2009-04-08 13:12 ` Anthony Liguori
2009-04-08 13:25 ` Glauber Costa
2009-04-08 16:34 ` [Qemu-devel] " Jan Kiszka
2009-04-08 16:41 ` Glauber Costa
2009-04-08 17:02 ` Jan Kiszka
2009-04-08 17:06 ` Glauber Costa
2009-04-08 17:20 ` Jan Kiszka
2009-04-08 17:23 ` Glauber Costa
2009-04-08 17:25 ` Glauber Costa
2009-04-08 17:39 ` M. Warner Losh
2009-04-08 17:44 ` Glauber Costa
2009-04-08 17:57 ` M. Warner Losh
2009-04-08 17:47 ` Paul Brook
2009-04-08 18:07 ` Glauber Costa [this message]
2009-04-08 18:58 ` Anthony Liguori
2009-04-08 18:57 ` Anthony Liguori
2009-04-08 19:03 ` Glauber Costa
2009-04-08 17:31 ` Paul Brook
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=5d6222a80904081107t55accbdag1d4621726cd3ba2c@mail.gmail.com \
--to=glommer@gmail.com \
--cc=glommer@redhat.com \
--cc=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).