This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Update new qemu-dm to spawn vncviewer

To: "Donald D. Dugger" <donald.d.dugger@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Update new qemu-dm to spawn vncviewer
From: Jeremy Katz <katzj@xxxxxxxxxx>
Date: Thu, 20 Jul 2006 16:45:41 -0400
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 20 Jul 2006 13:44:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060713040439.GA4099@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060713040439.GA4099@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2006-07-12 at 21:04 -0700, Donald D. Dugger wrote:
> 1)  Add `vncviewer' as an option to `qemu-dm' to spawn a `vncviewer' process.

Doesn't it make sense to push these sorts of changes to Fabrice and not
include them as a Xen patch until they're included in upstream qemu?
Otherwise, how do we avoid ending up back in the same place where we
have a huge pile of Xen specific patches making it very difficult to
rebase to a new version of qemu?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>