Subversion is a revision control tool, not a document sharing tool, and as
such it requires a certain discipline to use it. The user decides when to
commit changes and adds comments to describe those changes, and the user
decides when to update their working copy with changes from others. These
things cannot be automated. For plain text files subversion will merge
changes when a file is changed both locally and remotely; it cannot do that
with binary formats such as Office documents. Even when the files are
mergeable it requires communication between users to make sure they are not
working on the same parts of the same files.
For document sharing by non-technical users there are better solutions. I
know nothing about One Drive, but Google Docs works well. All changes are
saved automatically and if two users are editing the same doc they can each
see the other's changes happening.
Horses for courses as they say.
Simon
On 11 October 2014 02:44, Jerry Johns <jerrylanejohns_at_gmail.com> wrote:
> My company is thinking about using an alternative to SVN for MS Office
> document management.
>
>
>
> The biggest complaint is that non-technical people forget to check for
> repository updates or don’t commit after making changes to local files and
> this affects other people using those documents.
>
>
>
> I want to keep SVN instead of going with something like One Drive for
> Business, etc.
>
>
>
> Are there tools or options that would extend the functionality of Commit
> Monitor, for example, so that it keeps the local copy in sync?
>
>
>
> Thanks.
>
> Jerry
>
>
>
>
>
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3089773
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-10-11 11:09:33 CEST