From: Paul Larson <plars@linuxtestproject.org>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: RE: bitkeeper gone in 2 weeks - which RCS?
Date: Mon, 20 Jun 2005 15:39:56 -0500 [thread overview]
Message-ID: <1119299996.5380.24.camel@localhost.localdomain> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282262@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1511 bytes --]
On Wed, 2005-06-15 at 22:35 +0100, Ian Pratt wrote:
> BTW: We now run our own bkd because bkbits.net hasn't been very reliable
> recently. the unstable tree is available as
> bk://xenbits.xensource.com/xen-unstable.bk
> If you don't want to use bk, the open source bk-client and sourcepuller
> both work fine against it. I expect we'll continue to mirror stuff
> through to BK regardless.
>
> Hopefully we'll get a hg mirror on xenbits.xensource.com soon as well.
Since it looks like things are leaning more towards mercurial at the
moment, I decided to check it out. I hadn't previously paid much
attention to it since I could see that any projects were making use of
it and thought it was just too early in development to be practical. I
have to admit I was very impressed with several aspects of it, but it
does seem to be lacking in a number of areas as well.
I don't know if this feature is important to anyone but me, but hg
currently doesn't allow you to pull a specific revision, making testing
back through versions to find the point where something broke very
difficult:
-----------------------
>* Paul Larson <plars at linuxtestproject.org> [20050620 20:14]:
> >Is there currently a way to pull a specific revision? If not, is this
> >feature planned to be available soon?
>It is planned, but I think there is no schedule for implementation
>yet.
-----------------------
--
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-06-20 20:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 21:35 bitkeeper gone in 2 weeks - which RCS? Ian Pratt
2005-06-15 21:45 ` Andrew Thompson
2005-06-16 2:56 ` Rusty Russell
[not found] ` <mailman.1118871375.26501@unix-os.sc.intel.com>
2005-06-16 18:34 ` Arun Sharma
2005-06-20 20:39 ` Paul Larson [this message]
2005-06-20 20:44 ` Rik van Riel
2005-06-20 20:54 ` Josh Triplett
2005-06-20 21:01 ` Andrew Thompson
2005-06-20 21:28 ` Paul Larson
[not found] ` <mailman.1119300279.12847@unix-os.sc.intel.com>
2005-06-20 21:03 ` Arun Sharma
2005-06-20 21:08 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 0:16 Soh Tk-r28629
2005-06-21 0:29 ` Matt Mackall
2005-06-15 22:11 Ian Pratt
2005-06-16 1:16 ` Matt Mackall
2005-06-16 1:21 ` Rik van Riel
2005-06-15 23:03 ` Christopher Li
2005-06-16 11:36 ` Theodore Ts'o
2005-06-15 19:45 Ian Pratt
2005-06-15 20:10 ` Rik van Riel
2005-06-14 19:09 Rik van Riel
2005-06-14 19:26 ` Paul Larson
2005-06-14 19:27 ` Ronald G. Minnich
[not found] ` <mailman.1118777276.15947@unix-os.sc.intel.com>
2005-06-14 19:43 ` Arun Sharma
2005-06-14 19:50 ` Paul Larson
2005-06-14 19:58 ` Arun Sharma
2005-06-14 23:31 ` aq
2005-06-14 23:50 ` Rusty Russell
2005-06-15 7:09 ` Michael Paesold
2005-06-16 2:37 ` Ronald G. Minnich
2005-06-16 11:51 ` David Hopwood
2005-06-15 19:18 ` Rik van Riel
2005-06-14 19:52 ` Ronald G. Minnich
2005-06-14 19:54 ` Arun Sharma
2005-06-15 7:51 ` Gerd Knorr
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=1119299996.5380.24.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--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.