kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 26 Mar 2009 13:19:57 -0500	[thread overview]
Message-ID: <49CBC74D.70306@codemonkey.ws> (raw)
In-Reply-To: <49CB5448.9060203@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>> Hi Avi,
>>
>> I spent some time today putting together an approximation of the KVM 
>> stable release based on QEMU 0.10.x.  In principle, it's not too bad 
>> at all because it's just a matter of creating a branch in 
>> kvm-userspace that's based a kvm commit sometime after the QEMU 
>> 0.10.x release but before the next qemu-cvs merge you did that 
>> happened post QEMU 0.10.x.  Basically, it was a merge of 72ee81f and 
>> ddecccc.
>>
>> The problem for me is pulling in the QEMU stable fixes.  You don't 
>> have a branch that tracks the QEMU stable tree and I can pull in the 
>> QEMU stable git tree without rewriting history since the directory 
>> layout is different.
>>
>> But if you created a qemu-svn-stable branch that followed the QEMU 
>> stable tree in kvm-userspace, like the qemu-cvs branch follows trunk, 
>> then it would be pretty easy to create and maintain a kvm_stable_0_10 
>> branch of whatever you'd like to call it in kvm-userspace.
>>
>> Any chance you could do this?  I suspect it's just a matter of 
>> creating the branch based off of the qemu-cvs tree at ddecccc and 
>> then doing a git-svn fetch.
>>
>
> I pushed this under the old naming convention, as kvm-userspace.git 
> maint/2.6.30.  I'll rename it once I convert the repo.
>
>
Sweet, thanks!

Regards,

Anthony Liguori

      reply	other threads:[~2009-03-26 18:20 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
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 [this message]

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=49CBC74D.70306@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).