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/
Home Products Support Community News


Re: [Xen-devel] July 1 (no bk day) almost here

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] July 1 (no bk day) almost here
From: aq <aquynh@xxxxxxxxx>
Date: Thu, 30 Jun 2005 09:41:59 +0900
Cc: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Jun 2005 00:40:51 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iF+i/UETp6nTwEm09U8sSzC/3q2c+MnkGYDmtwKHDBZVRJ9BS25y/il0mIftY/XjzbROrneEVIG/nNRFQ48UBqT7IwFmgBrNn536N/QV5KiHrYFhMCMZC4LEOsqqtFrLuiVLK/SpuzZG4zmpnGC1/6trdkp/ch3w+vsG7/OQFS4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282437@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: <A95E2296287EAD4EB592B5DEEFCE0E9D282437@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 6/30/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> > Did I miss a posting on the plans for what the Xen team will
> > be doing starting Friday as far as source code management?
> > Does the Xen team have licenses for bk?
> Until the middle of last week, we were planning on running mirrored
> bitkeeper and mercurial trees. However, our current understanding is
> that we'd need a BK licence for all the mercurial users who's changesets
> we were automatically importing into BK. This clearly isn't going to
> scale, so we've had to abandon it.
> So, the new plan is a big-bang switch over to mercurial. There's been a
> lot of effort invested in this by Michael and James, and it looks like
> we'll be good for a public go-live Thursday morning -- I'll send out an
> email detailing where the repositories are, and a 'getting started
> guide' prepared by Andrew that describes the mercurial equivalents of
> simple bk commands. We have a mercurial patchbot that will start sending
> out messages to the changelog mailing list as soon as we make the
> switchover.
> Pretty much all the revision history information in the BK repository
> has successfully been imported into mercurial. Various of us have been
> playing around with mercurial for a while now, and although it's a step
> backwards from bitkeeper, its currently quite usable, and improving
> fast. The mercurial developers have been very responsive in fixing minor
> bugs and adding features we've requested, so we think this is the best
> way forward. Rest assured we've spent a great deal of time investigating
> the alternatives...

what a great news. i cannot wait. isnt Thursday today ? ;-)


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>