All of lore.kernel.org
 help / color / mirror / Atom feed
From: aq <aquynh@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: "Magenheimer,
	Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
	xen-devel@lists.xensource.com
Subject: Re: July 1 (no bk day) almost here
Date: Thu, 30 Jun 2005 09:41:59 +0900	[thread overview]
Message-ID: <9cde8bff050629174113aed440@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282437@liverpoolst.ad.cl.cam.ac.uk>

On 6/30/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> 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 ? ;-)

regards,
aq

  reply	other threads:[~2005-06-30  0:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 21:55 July 1 (no bk day) almost here Ian Pratt
2005-06-30  0:41 ` aq [this message]
2005-06-30  0:46 ` Rik Van Riel
  -- strict thread matches above, loose matches on Subject: below --
2005-06-29 19:42 Magenheimer, Dan (HP Labs Fort Collins)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9cde8bff050629174113aed440@mail.gmail.com \
    --to=aquynh@gmail.com \
    --cc=dan.magenheimer@hp.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.