#32 Set just binaries writeprotected

[Michael Herrmann]

There are projects in their the binary and the source
code files are mixed.

You can not use the advantages (eg. merging) of
cvs,
if you choose pessimistic locking to "protect" the
binaries

You can use the advantages of cvs, if you choose
optimistic locking,
but the binaries are not "proteced".

With this feature you can have both advantages
together,
using eg. merging an protecting the binaries.

For example:
/develop
main.cpp -rw
main.h -rw
bild1.jpg -r

To modify bild1.jgp you had to use the edit
(fixed "edit -c" in .cvsrc) command of WinCVS
to remove the wirte protection. Nobody is able to
modify bild1.jpg at this time.
After commiting ("commit -c" also fixed in .cvsrc)
everyone is able to modify the file again.

To modify main.cpp or main.h "just alter it" (by
using update) and commit if you are ready.
CVS is able now to merge this files.

Files with those extensions where not
writeprotected,
if "checkout readonly" in the global preferences in
wincvs.exe is selected.

This feature is easy to activate.
Simply copy the file .writeable in your
homedirectory
and adapt it to your needs.

MHE. mh-metzingen@t-online.de

[Michael Herrmann]

Feature to use both locking systems (optimistic and pessimistic) in one projekt.