Hi Stephane,

Welcome to the group!

It sounds to me like you're viewing the Repository and are editing
files from there.

In order to have a working area where you can edit files and then
commit, revert and update, you'll need to "Checkout" a working copy
from your repository and work from in there.

Regardless of the repository being local, conceptually it should be
treated just as a repository located on a server somewhere remotely.
The only actions people typically do directly to the repository
(instead of in a working copy) are:

- finding a folder to check out
- creating branches and tags
- reorganizing folders
- viewing previous revisions of the entire repository

Everything else that people typically do to the files that are under
version control, such as editing, saving, committing, reverting and
updating is normally done from a working copy.

I hope that helps clear things up a bit,

All the best,
- Dirk

the Versions team

On Jun 1, 2:35 pm, Stephane <[email protected]> wrote:
> I am presently looking at Versions to work on word documents that are
> part of an ISO 9001 master file.
>
> We are typically required to show revisions/changes/history at the
> document level (exact edits are not always relevant, as long as the
> note attached to the new version is sufficiently meaningful).
>
> I think svn and versions for that matter would work quite well for
> this purpose. I downloaded the demo version and configured a test
> project with all my word files in it.
>
> Only problem is, when I double click on the word file, and perform my
> edits and save them, the file in the main versions folder does not
> change. After investigating, I realized that I am editing a temporary
> copy of that file every time I double click on it (created in a
> temporary folder).
>
> Soooo, I must be doing something wrong, correct? It does not matter
> whether I double click on it or open the file via the popup menu and
> its 'Open with...' item, every single time word opens a temporary copy
> of the file.
>
> Also, I realized that within the project both the 'Update' and
> 'Commit' buttons are grayed out... FYI, the project was created as a
> local repository.
>
> Any help appreciated. Maybe this isn't the right tool?
>
> Thanks,
>
> Stephane

-- 
You received this message because you are subscribed to the Google Groups 
"Versions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.

Reply via email to