George Michaelson <ggm@apnic.net> writes:
>>How about one of the newer attempts, subversion?  I recently had a
>>project with it, but since I was only using client side, I have no
>>idea what the server side is like.
>
> Server side is ... strange. the files are held either as berkeley .DB file
> (singular, entire repositary) or as split files to provide faster service,
> but not in any 1:1 relationship to the files of the 'project' in question.

You don't need to use .db files, actually -- you can use the fsfs back
end as well.

> one corrupt bit, and you risk loosing the entire held state. It has a
> textual dump format but for a large project, with many years history and
> branches, this would be quite costly to hold online.

It isn't really. I've done it at a client and it worked out fine. I
rigged it so the commit script did incremental text backups, too.

Perry