From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: Stable branch releases?
Date: Mon, 09 Feb 2009 21:34:47 +0200 [thread overview]
Message-ID: <49908557.7050504@redhat.com> (raw)
In-Reply-To: <49908368.4010707@us.ibm.com>
Anthony Liguori wrote:
> Hi Avi,
>
> Since a number of people are using the maint/2.6.29 branch, perhaps we
> could start doing releases from it? For instance, a kvm-74.1,
> kvm-74.2, etc. set of releases. Likewise, when we start maint/2.6.30,
> a new set of stable releases could follow.
Yes, I want to do that. One question is what to call these releases,
though.
I'd like to keep the kernel part synced with 2.6.x.y for as long as
that's maintained. Perhaps we can call these releases kvm-stable-x.y
(though it would cause confusion with kvm-xx). So, users of
kvm-stable-x.y would be running the same code as users running
Linux-2.6.x.y with the bundled kvm modules.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-02-09 19:34 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 [this message]
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
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=49908557.7050504@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.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.