From: Alex Baretta <alex@barettadeit.com>
To: caml-list@yquem.inria.fr,
Ernesto Ferrari <ernesto@barettadeit.com>,
Paolo Donadeo <paolo@barettadeit.com>
Subject: Re: [Caml-list] [OT] Rant about VCS: Conclusions
Date: Tue, 21 Dec 2004 10:07:58 +0100 [thread overview]
Message-ID: <41C7E7EE.6030709@barettadeit.com> (raw)
In-Reply-To: <20041218092716.18ca0ed7.ocaml-erikd@mega-nerd.com>
Erik de Castro Lopo wrote:
> On Fri, 17 Dec 2004 22:37:53 +0100
> Sven Luther <sven.luther@wanadoo.fr> wrote:
>
>
>>We have had good success with subversion,
>
>
> I looked at subversion before deciding on Arch. ... This allows me to
> run a couple of parallel developement branches, share those that
> need to be with other external developers and merge acorss the
> branches pretty much at will.
>
> I have not seen another source contol system which handles
> branches as nicely as Arch.
>
> Erik
Paul Snively wrote:
> It really does sound as though you're edging from "version control"
> into "configuration management." If that's the case, you may want to
> look at Arch and its surrounding tools. In particular, the
> documentation at
> <http://www.gnu.org/software/gnu-arch/tutorial/multi-tree-
> projects.html>, "Multi-tree Projects and Configuration Management,"
> might be helpful to you.
There seems to be some agreement on the fact the "Configuration
Management Tool of Choice for Discriminating Software Company" is Arch.
Our project seems complicated enough to seriously consider moving to arch.
We have currently reimplemented our project's storage as a
non-denumerable set of darcs repositories, distributed in a
discontinuous manner over our company's network. I envision a
significant risk of complexity explosion, because darcs only supports
branches as duplicate repositories, which sounds like a nightmare.
However, darcs is about as much as would fit in before Christmas. Maybe
Santa Claus will put a working arch repository under my Christmas tree...
Alex
--
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL
tel. +39 02 370 111 55
fax. +39 02 370 111 54
Our technology:
The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/>
The FreerP Project
<http://www.freerp.org/>
next prev parent reply other threads:[~2004-12-21 9:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 17:07 [OT] Rant about VCS Alex Baretta
2004-12-17 18:42 ` [Caml-list] " Paul Snively
2004-12-17 19:28 ` Yaron Minsky
2004-12-17 20:13 ` Erik de Castro Lopo
2004-12-17 21:37 ` Sven Luther
2004-12-17 22:27 ` Erik de Castro Lopo
2004-12-18 9:28 ` Sven Luther
2004-12-18 9:49 ` Erik de Castro Lopo
2004-12-18 14:45 ` Sven Luther
2004-12-18 20:03 ` Erik de Castro Lopo
2004-12-18 9:52 ` Erik de Castro Lopo
2004-12-18 14:45 ` Sven Luther
2004-12-18 11:24 ` Richard Jones
2004-12-18 15:01 ` Sven Luther
2004-12-18 15:22 ` Richard W.M. Jones
2004-12-18 15:35 ` Richard W.M. Jones
2004-12-18 15:39 ` Sven Luther
2004-12-21 9:07 ` Alex Baretta [this message]
2004-12-21 22:03 ` [Caml-list] [OT] Rant about VCS: Conclusions Blair Zajac
2004-12-21 22:36 ` Erik de Castro Lopo
2004-12-21 23:19 ` David Brown
2004-12-21 23:47 ` Erik de Castro Lopo
2004-12-18 0:48 ` [Caml-list] [OT] Rant about VCS skaller
2004-12-18 11:25 ` henri dubois-ferriere
2004-12-18 15:03 ` Sven Luther
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=41C7E7EE.6030709@barettadeit.com \
--to=alex@barettadeit.com \
--cc=caml-list@yquem.inria.fr \
--cc=ernesto@barettadeit.com \
--cc=paolo@barettadeit.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