From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Glauber Costa <glommer@gmail.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: Stable branch releases?
Date: Wed, 11 Feb 2009 07:13:26 -0600 [thread overview]
Message-ID: <4992CEF6.2020904@us.ibm.com> (raw)
In-Reply-To: <4992C023.2030004@redhat.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>>
>> Yes, this would be IMHO the best overall solution. Can we take
>> kvm-userspace maint/2.6.29 and call it qemu-kvm-0.9.1-1? Most users
>> don't need newer kernel modules if they have a relatively recent distro.
>>
>
> Right, that's another advantage of split repos.
>
> I wonder about splitting the ordinary kvm-xx releases? It means
> doubling the download/build/install cycle, but it will increase
> similarity to the stable releases.
I was going to suggest that to but then wanted to avoid complicating
things. I think it's the right model.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-02-11 13:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 19:26 Stable branch releases? Anthony Liguori
2009-02-09 19:34 ` Avi Kivity
2009-02-09 19:39 ` Anthony Liguori
2009-02-09 19:49 ` Glauber Costa
2009-02-09 20:10 ` Avi Kivity
2009-02-09 20:44 ` Anthony Liguori
2009-02-11 12:10 ` Avi Kivity
2009-02-11 13:13 ` Anthony Liguori [this message]
2009-02-11 13:18 ` Avi Kivity
2009-03-09 10:35 ` Avi Kivity
2009-03-09 13:52 ` Anthony Liguori
2009-03-09 14:39 ` Avi Kivity
2009-03-09 15:56 ` Anthony Liguori
2009-02-09 20:07 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2012-04-11 17:07 Ian Campbell
2012-04-11 18:41 ` Keir Fraser
2012-04-11 23:11 ` Wei Huang
2012-04-12 8:13 ` Keir Fraser
2012-04-11 18:49 ` Stefano Stabellini
2012-04-12 10:47 ` Ian Jackson
2012-04-12 14:59 ` Ian Campbell
2012-04-12 16:04 ` Keir Fraser
2012-04-12 16:30 ` Ian Campbell
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=4992CEF6.2020904@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@gmail.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.