From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LrcBM-0004Pp-34 for qemu-devel@nongnu.org; Wed, 08 Apr 2009 14:07:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LrcBH-0004PX-P0 for qemu-devel@nongnu.org; Wed, 08 Apr 2009 14:07:27 -0400 Received: from [199.232.76.173] (port=53130 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LrcBH-0004PU-I1 for qemu-devel@nongnu.org; Wed, 08 Apr 2009 14:07:23 -0400 Received: from mail-qy0-f111.google.com ([209.85.221.111]:42570) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LrcBH-0006kY-4w for qemu-devel@nongnu.org; Wed, 08 Apr 2009 14:07:23 -0400 Received: by qyk9 with SMTP id 9so414887qyk.4 for ; Wed, 08 Apr 2009 11:07:21 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <200904081847.07083.paul@codesourcery.com> References: <5d6222a80904081006w65228ac7k3b6e759e08f4c8b3@mail.gmail.com> <5d6222a80904081025j1644b6bay17d1ff942247971@mail.gmail.com> <20090408.113954.-1962672847.imp@bsdimp.com> <200904081847.07083.paul@codesourcery.com> Date: Wed, 8 Apr 2009 15:07:20 -0300 Message-ID: <5d6222a80904081107t55accbdag1d4621726cd3ba2c@mail.gmail.com> Subject: Re: [Qemu-devel] Re: start qemu failed with --enable-kvm -vga std From: Glauber Costa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: glommer@redhat.com, qemu-devel@nongnu.org On Wed, Apr 8, 2009 at 2:47 PM, Paul Brook wrote: > On Wednesday 08 April 2009, M. Warner Losh wrote: >> In message: <5d6222a80904081025j1644b6bay17d1ff942247971@mail.gmail.com> >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Glauber Costa 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? =C2=A0It is unlikely to be merged into stable, so let's commit it t= o >> 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 sta= ble > branch that isn't also fixed on the development branch. If the changes ar= e > 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. --=20 Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act."