On Wed, Aug 27, 2014 at 10:28 AM, Zé <jose.pas...@gmx.com> wrote:
> >
>
> And I hate to repeat myself, but I'll repeat for the third time this
> question: if file:// is not intended to be used, then what are the available
> options for those who need a version control system and can't set up a
> server?
The answer isn't going to change, no matter how many times we repeat
it. Subversion works with file:// access, but it can't protect you
from all the other ways that the filesystem allows write access and it
can't work that way without write access. If that bothers you, set up
a server - or just keep good backups and realize that if you switch to
a backup repository copy that is not exactly in sync, you need to
check workspaces back out again. If you really can't set up a
server you might be better off with one of the version control systems
that are intended to have distributed copies - and keep several,
updated frequently. Subversion's real advantage is where you want
one centrally-managed and authoritative copy. But I don't understand
why you "can't" set up a server when the advantages it provides seem
important to you.
--
Les Mikesell
lesmikes...@gmail.com
