Mark Phippard wrote:
>Peter McNab <mcnab_p@melbpc.org.au> wrote on 04/14/2005 11:43:12 AM:
>
>
>
>>Simon Large wrote:
>>
>>
>>
>>>>Once we update (synchronize) our WC with the Head, then it's up to
>>>>ourselves to be aware that from now on that there may be read-only
>>>>files i.e. files locked by another user present in our WC(s).
>>>>At the same time, we need to be aware of the locks we hold so they can
>>>>be released ASAP.
>>>>
>>>>
>>>>
>>>>
>>>Don't be misled. The file in your WC will be read-only even if no-one
>>>has a lock. It only becomes writable when _you_ have the lock.
>>>
>>>Simon
>>>
>>>
>>>
>>>
>>>
>>Now I'm worried, how do they get read-only if nobody has a lock?
>>Are we shortly going to be obliged to go around our WC's making things
>>
>>
>>writeable just to get work done?
>>
>>
>
>The whole read-only thing is only somewhat related to locking. You can
>use lock/unlock on any file unless a hook prevents it. This does nothing
>to make a file read-only or writable. The file will always be writable as
>it is today. If you try to do a lock and someone else has a lock, your
>lock request will fail. Likewise, if you try to commit and someone else
>holds a lock your commit will fail. But you can acquire the lock later,
>merge the changes and then commit.
>
>
>
So if I understand correctly, merge able things like source files will
stay writable in the WC, as they currently are.
Is that regardless of whether they are locked by someone else and I've
done an update?
I can only see a productive use for locking on text type files while
resolving conflicts.
>The secondary issue was intended for unmergeable files like graphics, but
>could be used for anything. For these types of files, a property can be
>set named svn:needs-lock. When this property exists on a file, when you
>do operations like checkout/update the file will be made read-only in your
>WC as a hint that you need to lock it. When you run the Lock option, it
>will get the lock AND become writable. When you commit and unlock, the
>file go back to read-only.
>
>
>
Now that makes sense
>People that want SVN to work like VSS or PVCS might set this property on
>all files to turn it into a fully locking system.
>
>Mark
>
>
>
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 14 18:04:47 2005