cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] RCS sandbox
Date: Fri, 28 Sep 2007 06:34:59 +0200	[thread overview]
Message-ID: <46FC8473.1060008@ubuntu.com> (raw)

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.

It is my understanding that our options are also limited to what our hosting
service can provide but David should be able to confirm this.

One (and i repeat - one -) of the option is to switch to git.

To give developers an easy way to try it out, I did a test import of the entire
CVS archive (including history and branches) in git.

So what is the deal here:

- the repository has been imported once for testing:
 * it is not syncing regularly with CVS.
 * it is not complete (lacks some info in the commit logs, it does not map CVS
user names to git sign-off).
 * the import history has not been verified.

- the repository is hosted on a sandbox on my personal workstation:
 * you can use git:// and http:// checkouts.
 * you can commit (*).
 * all changes will be dropped *if* we will ever switch to git.
 * there is no guarantee that my workstation will be up 24/7.
 * bandwidth to my workstation is nothing spectacular so be patience (**).

So if you want to try it out you can browse everything using:

http://git.fugedabout.it/

(*) In order to get an account on the sandbox, please mail get in touch via
email (or IRC) with me. (PS: I will give accounts only to people that have CVS
write access)

(**) my workstation is also Ipv6 enabled. In some setups you might want to make
sure to use Ipv4 on your end if you notice an extremely long timeout on your
side (it usually a symptom of a broken hardware or setup on your side ;)).

Have fun
Fabio

-- 
I'm going to make him an offer he can't refuse.



             reply	other threads:[~2007-09-28  4:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  4:34 Fabio Massimo Di Nitto [this message]
2007-09-28 15:04 ` [Cluster-devel] RCS sandbox Lon Hohberger
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=46FC8473.1060008@ubuntu.com \
    --to=fabbione@ubuntu.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).