From: Paul Larson <plars@linuxtestproject.org>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: bitkeeper gone in 2 weeks - which RCS?
Date: Tue, 14 Jun 2005 14:26:45 -0500 [thread overview]
Message-ID: <1118777205.2404.282.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0506141508200.25723@chimarrao.boston.redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 565 bytes --]
On Tue, 2005-06-14 at 15:09 -0400, Rik van Riel wrote:
> Since bitkeeper will become unusable for most of us in 2
> weeks, I'm wondering what revision control system Xen will
> be using by then.
>
> I'd like to get familiar with the tools and get a changelog
> bot written before the switchover ;)
I've been holding off on some xentest changes for the same reason. I'd
like to give it the ability to pull snapshots from an SCM as soon as we
are using a free one.
--
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-14 19:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 19:09 bitkeeper gone in 2 weeks - which RCS? Rik van Riel
2005-06-14 19:26 ` Paul Larson [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-06-15 19:45 Ian Pratt
2005-06-15 20:10 ` Rik van Riel
2005-06-15 21:35 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
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
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-21 0:16 Soh Tk-r28629
2005-06-21 0:29 ` Matt Mackall
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=1118777205.2404.282.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=riel@redhat.com \
--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.