[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: using DVCS
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Re: using DVCS |
Date: |
Fri, 27 Feb 2009 16:41:06 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Mon, Feb 23, 2009 at 08:24:11PM +0100, Christoph Becker wrote:
> In the German journal c't there was an interesting article on mercurial
> last year.
> A main source seems to have been the following book
> Bryan O’Sullivan, Distributed revision control with Mercurial:
> http://hgbook.red-bean.com/hgbook.pdf
> Mercuial (http://www.selenic.com/mercurial/wiki/) is open source. It is
> written python for 95 % and for the rest in c.
>
> Here some citations from Bryan O’Sullivan's book
...
> Indeed, the Windows GUI-Support for Subversion with Tortoise ist great.
> But what if you have more than one developer and one of them wants to
> play around and work on the project in his vacation, while not having
> any internet connection for many days? What if one developer likes to
> work on the project at some nice place in the countryside or on a train,
> where there is no cheep high speed internet connection? Then you do get
> forks and a need for merging overlapping development. A distibuted
> version control system seems to make life easier in such situations.
It does and in the not-too-distant future we really need to
switch to one of them. In terms for impact and
unlikelyhood-to-go-unmaintaned I would opt for GIT, maybe
via SVN.
So far we haven't had much of a need to coordinate much
parallel development yet the reason for which I doubt to lie
in CVS all by itself.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346