On Thu, Dec 12, 2013 at 4:02 AM, Branko Čibej <br...@wandisco.com> wrote:
>
>> Some things... But not the things you really need to complete any
>> amount of actual work - like updates and commits.
>
> You're forgetting diff. If you use Subversion daily, you've become so
> used to it being local that you can't appreciate how slow it would be
> without locally cached pristine copies.
But (a) it is trivial to make your own snapshot copy of file versions
if you expect to need them (as you must anyway for any offline state
except 'as checked out' and 'completely current'. And (b), I'm as
likely to want to diff against a different branch or someone else's
subsequent commit as my own pristine version (and no, that isn't
unreasonably slow...). Also, most of this discussion is related to
scenarios where active development is not happening - like the jenkins
build server example.
> Anyway, this thread has gone way off any kind of reasonable topic. The
> short answer to the original poster is that Subversion is not intended
> to be a replacement for rsync. You can take that as a hint as to what
> the solution to your problem might be.
But it _was_ intended to be a replacement for cvs, which has nowhere
near the client-side resource requirements.
--
Les Mikesell
lesmikes...@gmail.com
