Ron Wilson <ronw.mrmx@...> writes:
>
> This is actually a s\Subversion issue, rather than TSVN.
>
> I'm not sure just what you are looking to do, but if you are intending
> to use a Lock-Modify-Checkin mode of work, then you can add the
> property, svn:needs-lock, to files you want to require to be locked
> before modifying.
>
> Normally, this owuld only be done to files where merging modifications
> is not possible, such as graphical images like GIF, JPEG and PNG
> files, or other binary formats. (while I'm not sure of SVN (or TSVN)
> supports it, some binary formats are merge-able)
>
> Otherwise, it is not necessary - and generally discouraged - to
> require files be locked. (see section 2.2 in the manual for the pros
> and cons of locking verses merging)
>
> When a file is "flagged" for locking, then the working copy of that
> file will (after or check out or update) be read only, unless the
> working copy has possession of the lock on that file.
>
>
Thanks for your reply.
I just feel "not correct" to modify the source code without reserve the edit
right, after using WinCVS for such a long time. maybe I just should adapt to
the way of SVN. :)
Regards!
sandodo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Sep 6 05:36:55 2007