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] [PATCH] remove use of get_gendisk in blkfront

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] remove use of get_gendisk in blkfront
From: Josh Boyer <jwboyer@xxxxxxxxx>
Date: Wed, 9 Nov 2005 07:59:55 -0600
Cc: Jeremy Katz <katzj@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Wed, 09 Nov 2005 14:00:05 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=teTPII/BvEmVe4xSG9TAlwRQr1yMpw2GeLe2WRDV9tmI+gAxoGHasErZ6SFXmvvAQzn944xuOYjH+08GBtSbf3ewEuS737seKc1RP+AWJbBOQ2TbvCCKMAOULH6ECDUfVF26acm4d1x7JmUMkjpnPAXWjtTlU8e64faMUm5ITzk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D32E863@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D32E863@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 11/9/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
>
> [Aside: it would be really nice if there was some tool that pulled
> patches off a mailing list and fed them into something like bugzilla,
> along with all the coments associated with a patch. It should also watch
> the changelog list and update the status as 'APPLIED' when appropriate.
> At any time an author could withdraw/supercede a patch, and a maintainer
> could reject/keep-on-file. A really smart system would also keep patches
> fresh by trying to rebase them, or at least note if they still apply
> cleanly.]

Jeremy Kerr wrote a tool called patchwork that sort of does that. 
It's not nearly as full featured as you'd like, but the basic idea is
there.

The project page is at:
http://www.ozlabs.org/~jk/projects/patchwork/

And an example of it running is at:
http://patchwork.ozlabs.org/linuxppc64/

josh

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