From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-kmod.git Date: Mon, 27 Apr 2009 17:56:41 +0300 Message-ID: <49F5C7A9.2070803@redhat.com> References: <49F5A5DD.4090504@redhat.com> <49F5BC78.6060505@lfarkas.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Farkas Levente Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34814 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755131AbZD0O4r (ORCPT ); Mon, 27 Apr 2009 10:56:47 -0400 In-Reply-To: <49F5BC78.6060505@lfarkas.org> Sender: kvm-owner@vger.kernel.org List-ID: Farkas Levente wrote: > hi, > i see this big reorganization of the sources (which is good), but does > it means that there will be separate tarball releases for kvm-kmod and > kvm userspace (which can be compiled without other tarball and git > commands)? > if yes, it means there'll be one kvm-kmod tarball or for each kernel > there will be a different tarball? > thanks There will be a qemu-kvm tarball (qemu only), kvm-kmod tarball (kernel module only, suitable for any supported host kernel), and kvm tarball (contains both of the above). -- error compiling committee.c: too many arguments to function