From: Jeremy Katz <katzj@redhat.com>
Subject: Re: [PATCH] Update new qemu-dm to spawn vncviewer
Date: Thu, 20 Jul 2006 16:45:41 -0400
Message-ID: <1153428341.4415.12.camel@aglarond.local>
References: <20060713040439.GA4099@los-vmm.sc.intel.com>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20060713040439.GA4099@los-vmm.sc.intel.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Donald D. Dugger" <donald.d.dugger@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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?

Jeremy