All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: bitkeeper gone in 2 weeks - which RCS?
Date: 15 Jun 2005 09:51:10 +0200	[thread overview]
Message-ID: <87r7f412j5.fsf@bytesex.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0506141508200.25723@chimarrao.boston.redhat.com>

Rik van Riel <riel@redhat.com> writes:

> 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 vote for either subversion or git.  subversion because it is
widely used (so I'd trust it not screw data) and it also seems to be
the cvs successor in the open source community.  git because it's used
to manage the linux kernel.  Quite a few of us also do kernel work, so
using the same tool for both xen and the linux kernel would be very
nice.

just by two cent,

  Gerd

-- 
-mm seems unusually stable at present.
	-- akpm about 2.6.12-rc3-mm3

  parent reply	other threads:[~2005-06-15  7:51 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
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 [this message]
  -- 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=87r7f412j5.fsf@bytesex.org \
    --to=kraxel@suse.de \
    --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.