From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Split kvm source tarballs
Date: Wed, 25 Mar 2009 08:44:58 -0500 [thread overview]
Message-ID: <49CA355A.6010803@codemonkey.ws> (raw)
In-Reply-To: <49CA3058.3040600@redhat.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>>
>> Hrm, I notice that for qemu-kvm, you basically just pulled out the
>> module source.
>>
>
> That's step 1.
>
>> What do you think about going a step further and building a proper
>> qemu repository?
>>
>
> Step 2. I have scripts that do that and will merge with Eduardo's
> script that also rewrites the qemu commit hashes to correspond to
> qemu.git on git.kernel.org.
That's what I figured. FWIW, the split tarballs work just fine for me.
It may be worth waiting to do step 2 until the IO thread is merged. I
think once that happens, we could probably do a sprint to get rid of
libkvm in kvm-userspace. That would certainly simplify things.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-03-25 13:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 14:21 Split kvm source tarballs Avi Kivity
2009-03-25 13:18 ` Anthony Liguori
2009-03-25 13:23 ` Avi Kivity
2009-03-25 13:44 ` Anthony Liguori [this message]
2009-03-25 16:47 ` Christoph Hellwig
2009-03-25 18:02 ` Avi Kivity
2009-03-25 18:17 ` Christoph Hellwig
2009-03-26 9:09 ` Avi Kivity
2009-03-26 22:48 ` Christoph Hellwig
2009-04-16 20:17 ` Christoph Hellwig
2009-04-18 22:13 ` Anthony Liguori
2009-04-19 8:26 ` Avi Kivity
2009-03-25 21:34 ` Anthony Liguori
2009-03-26 8:57 ` Christoph Hellwig
2009-03-26 18:19 ` Anthony Liguori
2009-03-26 22:48 ` Christoph Hellwig
2009-03-27 2:44 ` Anthony Liguori
2009-03-26 10:09 ` Avi Kivity
2009-03-26 18:19 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49CA355A.6010803@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.