>> Suppose a folder is up to date such that if you commit it there are no files changed or added in the commit dialog.
>> Now right click in the folder and lock all files.
>> Now in the commit dialog, all the files are ticked as if changed however, only the lock status has changed.
>> I would have expected this is not intended behavior.
>Yes, that's the intended behavior.
>Because you should not lock files if you don't work on them, so locking whole folders is a bad ides to begin with.
>And to remind you that you should release the lock when you commit, those locked files are all checked so when you commit, the lock is released.
>Stefan
Hi Stefan,
I can see how this would be a bad idea in some situations, however in this case I prefer the other way.
What I am doing is working on a file with a program which then can generate other files.
The whole folder should not have more that 1 person working on it at a time as the files are closely interrelated and cannot be merged - hence 'needs-lock' property is set.
At commit time, I would usually use the commit dialog as a rough check that only files I expect have changed, however it gives the appearance of all files changing even if I have done no work on them. I can't use the icon overlays for this as they are unreliable.
That there are so many different uses for TortoiseSVN is a testimony to how useful and reliable it is, but I can understand too that it is difficult for you when users want opposing features.
John
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2949992
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-20 01:44:55 CEST