From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alon Levy Subject: Re: [PATCH v2] kvm tool: add QCOW verions 1 read/write support Date: Thu, 14 Apr 2011 11:49:38 +0300 Message-ID: <20110414084938.GP16600@playa.tlv.redhat.com> References: <1302722762-30517-1-git-send-email-prasadjoshi124@gmail.com> <4DA6AA2F.2020306@redhat.com> <4DA6B0D8.3010706@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Kevin Wolf , Prasad Joshi , mingo@elte.hu, kvm@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com, levinsasha928@gmail.com, stefanha@linux.vnet.ibm.com To: Pekka Enberg Return-path: Received: from mx1.redhat.com ([209.132.183.28]:11592 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756818Ab1DNIuD (ORCPT ); Thu, 14 Apr 2011 04:50:03 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Apr 14, 2011 at 11:32:21AM +0300, Pekka Enberg wrote: > Hi Kevin! > > Am 14.04.2011 10:21, schrieb Pekka Enberg: > >> On Thu, Apr 14, 2011 at 11:02 AM, Kevin Wolf wrote: > >>> Have you thought about a way to actually share code with qemu instead of > >>> repeating Xen's mistake of copying code, modifying it until merges are > >>> no longer possible and then let it bitrot? > >> > >> No we haven't and we're not planning to copy QEMU code as-is but > >> re-implement support for formats we're interested in. > > On Thu, Apr 14, 2011 at 11:31 AM, Kevin Wolf wrote: > > Okay. I might not consider it wise, but in the end it's your decision. > > I'm just curious why you think this is the better way? > > Well, how would you go about sharing the code without copying in > practical terms? We're aiming for standalone tool in tools/kvm of the > Linux kernel so I don't see how we could do that. You mean you would not be ok with linking with anything other then glibc? > > Pekka > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html