[cvsnt] cvsnt for word doc version control

[Glen Starrett]

Noah wrote:
> I am looking for a more verbose response.  I've seen the website.  Maybe 
> a specific link because I am not able to find docs that address version 
> control and update handling with multiple participants.

Hi Noah -- There are multiple ways CVSNT can handle managing multiple 
people committing against the same repository.  The information is 
spread out across the website.

Primarily, I think you're looking for information on locking (or 
reserving), communication methods, and permissions.

With locking you can choose to have the server enforce strictly 
(exclusive edits) or cooperatively (with the -c option).  You can also 
choose concurrent access, but that is not recommended.  We recommend 
strict locking on all binary files.

Communication methods include notification email (can be configured to 
automatically email a group when a file is edited, committed, etc.) or 
looking at the current list of who has which files edited.

With permissions (Access Control Lists, or ACL), you can control who has 
access to what files, on which branch, and which operations they can do 
on them.

http://march-hare.com/cvsnt/newfeatures/

If you want more details on our commercial software and support 
offerings, email me directly and I'll be happy to answer your questions.


> here is the concern as mentioned by Tim from his post:

I believe this was all addressed by other posts.  Let me know if you 
still have questions.

Regards,

-- 
Glen Starrett
Technical Account Manager, North America
March Hare Software, LLC

http://march-hare.com/cvspro/