From: "Jan Beulich" <JBeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: full featured, fully bug-fix pv-ops branch?
Date: Mon, 09 May 2011 13:16:11 +0100 [thread overview]
Message-ID: <4DC7F72B020000780004064E@vpn.id2.novell.com> (raw)
Jeremy, Konrad,
stumbling over this once in a while (this time looking for where Dominic's
"blktap: Fix reference to freed struct request" patch ended up, without
any success so far) I wonder what pv-ops branch(es) is (are) supposed
to be the one(s) (e.g.) distros ought to use - that is, fully featured (at
least as far as non-experimental features go) *and* fully bug-fixed.
The branches XenParavirtOps on the wiki points to don't seem to be the
ones (some of them seem not to have a blktap implementation at all),
and gathering bits from various people's private trees can't be the
ultimate solution...
Thanks, Jan
next reply other threads:[~2011-05-09 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 12:16 Jan Beulich [this message]
2011-05-09 13:07 ` full featured, fully bug-fix pv-ops branch? Pasi Kärkkäinen
2011-05-09 21:06 ` Konrad Rzeszutek Wilk
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=4DC7F72B020000780004064E@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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).