Julian Elischer <[EMAIL PROTECTED]> writes:
> It has good points and bad points
> the bad point is that you can't work offline.
> the good point is that development in different branches doesn't
> slow each other down. (as it might in CVS).
> It also keeps track of edits that touch multiple files as a unit.

I'm working on porting the latest beta release of Subversion, which
does all that and more, and has much better diff support than
Perforce.  After using Perforce for my PAM work, I've come to the
conclusion that although it's a big step forward from CVS in one
direction (change management & branching), it's a big step backward in
almost every other direction.

See http://www.tigris.org/files/documents/15/48/svn-design.html for
details about the Subversion design.

(in order to make a proper Subversion port, though, we need a port of
the Apache Runtime - my port currently builds APR as part of the SVN

Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to