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-ppc-devel

Re: [XenPPC] Re: [Xen-devel] new repo layout?

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [XenPPC] Re: [Xen-devel] new repo layout?
From: Jimi Xenidis <jimix@xxxxxxxxx>
Date: Mon, 18 Jun 2007 13:40:58 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Hollis Blanchard <hollisb@xxxxxxxxxx>, James Bulpin <James.Bulpin@xxxxxxxxxxxx>, Aron Griffis <aron@xxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Jun 2007 10:39:02 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:subject:date:to:x-mailer:from:sender; b=Z9umGiLtMfH86buqlppPrkXFeo8v+KnIvE1j3s0+Ks8233C/rD4dFufpezjN1xfT9JmsnTKJuKv3C2nOZfM9bE0E9wbcPC3hffbVib82jJl/HMfdV7upeC8dSk5A1xUU5dItwCF+PlFI6BoPd7pHN/893Dir8fsE5sq23jrbHgw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:subject:date:to:x-mailer:from:sender; b=VkmNZUMA1u5betjy8aO0WmYxSsED0NgyfgrAa4ZhJ6b7RCYcu8lfE7uzRs+wH8Gy9NRAJyio8Hb7izgfkppnVmm2o6D5+hjHCdlyXOk+nyZ3Zt8Xg3apf5zEcTlG84xJAzBqkl5Mup3dwL5G5Tbtt3zdJRuirptb3neP91AGc9w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1180993129.5416.9.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070530214638.GA21589@xxxxxxxxx> <1180598644.29571.57.camel@xxxxxxxxxxxxxxxxxxxxx> <1180627325.16734.26.camel@basalt> <1180628637.29571.84.camel@xxxxxxxxxxxxxxxxxxxxx> <1180967986.6221.133.camel@bling> <1180973667.4041.18.camel@xxxxxxxxxxxxxxxxxxxxx> <1180977928.6221.144.camel@bling> <1180979173.29109.4.camel@basalt> <1180983761.6221.160.camel@bling> <1180984535.29109.6.camel@basalt> <1180993129.5416.9.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Ian,
Any chance you can wire up the email notifications again?
-JX

On Jun 4, 2007, at 5:38 PM, Ian Campbell wrote:

On Mon, 2007-06-04 at 14:15 -0500, Hollis Blanchard wrote:
This way we'll end up with common names like:

/xen-unstable.hg
/linux-2.6.18-xen.hg
/staging/xen-unstable.hg
/staging/linux-2.6.18-xen.hg
/ext/ia64/xen-unstable.hg
/ext/ia64/linux-2.6.18-xen.hg

Sound good?  Thanks,

Sounds good to me.

I'll look into making these changes tomorrow, with symlinks so the old
names remain valid hopefully.

(I presume you need someone at XenSource to do the moves for you?)

Ian.


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


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