From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] RCS sandbox
Date: Fri, 28 Sep 2007 11:04:26 -0400 [thread overview]
Message-ID: <1190991866.10032.8.camel@ayanami.boston.devel.redhat.com> (raw)
In-Reply-To: <46FC8473.1060008@ubuntu.com>
On Fri, 2007-09-28 at 06:34 +0200, Fabio Massimo Di Nitto wrote:
> Hi everybody,
>
> for sometime now there has been a strong indication (on IRC) that the project
> should move away from CVS to land on a more modern RCS.
> Before you start a flame war that foo is better than bar and so on, let me
> explain that we all understand the RCS of choice is always binded to people
> personal tastes and it is basically impossible to make everybody happy.
I would vote for Mercurial if I had a say.
However, I'm sure someone with a far stronger opinion would complain,
so, forget I said anything. In any case, I would like to recommend
restricting the possible choices to:
* git
* svn
* mercurial (hg)
Rationale: That's what closely-related projects use (Linux, openais,
Linux-HA).
-- Lon
next prev parent reply other threads:[~2007-09-28 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 4:34 [Cluster-devel] RCS sandbox Fabio Massimo Di Nitto
2007-09-28 15:04 ` Lon Hohberger [this message]
2007-10-02 5:27 ` [Cluster-devel] RCS sandbox - update Fabio Massimo Di Nitto
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=1190991866.10032.8.camel@ayanami.boston.devel.redhat.com \
--to=lhh@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).