WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] vt-d: Test device ass

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] vt-d: Test device assignability in xend, but defer actual assignment to qemu-dm.
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 21 Dec 2007 10:52:27 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, weidong.han@xxxxxxxxx
Delivery-date: Fri, 21 Dec 2007 02:55:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071220185242.GA755@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <200712122150.lBCLoO5K007539@xxxxxxxxxxxxxxxxxxxxx> <20071212215300.GA23453@xxxxxxxxxxxxxxxxxxxxxxx> <20071220185242.GA755@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
John Levon writes ("Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] vt-d: 
Test device assignability in xend, but defer actual assignment to qemu-dm."):
> This still isn't added ... Keir, should I bother? I don't think people
> will do anything unless you start enforcing it yourself :(

Perhaps it would be better to move the changelog to a file in the
source tree.  If we put our foot down just a little bit we could
reject (or fix up) patches that change the API but don't document it
properly.

Currently much of the documentation in the tree is out of date or
wrong but I'm hoping we can gradually improve this.  Where there is
good documentation, I think patches ought not to go in if they make
the docs wrong.

IME you can do one of (a) accept that a piece of documentation will
rot, (b) try to find someone to chase up afterwards, or (c) insist
that the doc changes have to accompany (or precede) the code changes.
At the moment we have (a), and there is unfortunately little chance of
(b).  I think a sprinkling of (c) would help :-).

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel