From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: full featured, fully bug-fix pv-ops branch?
Date: Mon, 09 May 2011 13:16:11 +0100
Message-ID: <4DC7F72B020000780004064E@vpn.id2.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.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>
List-Id: xen-devel@lists.xenproject.org

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