>
>
> 2) CVS is capable of having 'local' repositories. i.e. even if you
> don't have server you can wack in a directory, cvs init it and
> use it for version control / internal collaboration. SVN can't
> do this... can it? Local repositories really are useful, especially
> in situations where a code may have many developer chronologically
> though one a poor postdoc and his supervisor at any one time. A
> local repository remains an easily passable parcel, but one can
> still grep the cvs log to find out when/why something changed!
> (I know, I don't love this either, but it really is how people work)
>
of course you can create a local svn repository, just 'svnadmin create'
and use ra_local to access it. your client will need to be linked
against the berkeley db libraries, but that's the only restriction.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 11 19:05:59 2003