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-merge

RE: [Xen-merge] xen subarch

To: "Rik van Riel" <riel@xxxxxxxxxx>
Subject: RE: [Xen-merge] xen subarch
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 10 Oct 2005 23:10:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-merge@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 10 Oct 2005 22:08:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-merge-request@lists.xensource.com?subject=help>
List-id: xen-merge <xen-merge.lists.xensource.com>
List-post: <mailto:xen-merge@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-merge-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXNyXwIPFHpHQQrR1G9y8tJb7uRsAAE0a0g
Thread-topic: [Xen-merge] xen subarch
 
> > To try and kick things off, we've created a Linux mercurial 
> repo which 
> > has xen as a subarch of i386 and x86_64 :
> > http://xenbits.xensource.com/linux-2.6-xen.hg
> 
> $ hg clone http://xenbits.xensource.com/linux-2.6-merge.hg
> requesting all changes
> abort: HTTP Error 404: Not Found

Sorry, the two trees are:
http://xenbits.xensource.com/linux-2.6-xen.hg          (latest stable)
http://xenbits.xensource.com/ext/linux-2.6-merge.hg    (bleeding edge)
 
> > So, who's up for wading in and getting started with the 
> cleanup?  Who 
> > can help us keep the tree up todate with Linus'?
> 
> I'm interested, and I can probably get a few other people 
> here interested too...

Excellent!

> > Send me an ssh2 key if you want push rights to this tree, 
> or otherwise 
> > want other trees created as staging areas. We might as well use the 
> > xen-merge for patch review and discussion.
> 
> It would probably be a good idea if all patches (except 
> merges from Linus) would get reviewed.  OTOH, having review 
> after the fact on a changelog mailing list would probably work too.

Yep, the changelog deamon would require need some reworking to look new
csets up in a reference Linus tree to see whether they came from Linus
or not...

Ian

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