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.
On 9/5/07, sandodo <zouxiong@loewen.com.sg> wrote:
> Hi All,
>
> I am using tortoisesvn 1.4.3 and my subversion is 1.4.2
>
> I found that after I commit my files, they are not made read-only, not like
> what WinCVS does.
>
> Do I miss anything in the configuration or is there any new version which
> support this feature? And for the newest version of tortoisesvn: 1.4.5, does it
> support subversion 1.4.2?
>
> Thanks a lot in advance!
> sandodo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Sep 6 04:57:11 2007