Re: cvs commit: fptools/green-card/distrib INSTALL

Simon Marlow wrote:
 > Where do I start? :-)  No atomic commits, virtually impossible to find
 > out which other files changed in a given commit,

Well, this is what I meant by "transaction". For the latter problem
you can abuse the timestamp, it's not foolproof, but works most of the
time. The CVS viewer from Horde uses this approach, IIRC.

 > no versioning on directories or filenames,

OK, I forgot that one.

 > branching/merging that is a nightmare to use for anything
 > non-trivial,

Branching is easy in CVS, but merging is often not. Things are much
easier if one follows a few conventions (no CVS keywords, always merge
in a single direction, use tags), but the remaining complexity is
probably a sign of the mental complexity of the merging itself, not a
problem of CVS.

 > no distributed repositories, ...

Huh? CVS > 1.11 supports this, and we actually used it in my last
company: Parts of the development tree were accessible to hired
consultants via ssh, but not the "main" parts.

 > [ Subversion, Arch, Darcs comments omitted ]

But one of the main advantages of CVS should not be forgotten: There
is a *vast* amount of tool support for it. It works with almost every
IDE out there, dozens of CVS browers exist (e.g. the really cool
Cervisia stuff integrated in KDE's konqueror, several web-based ones,
etc.), it works via ssh, etc. etc.

Cheers,
    S.