On Fri, Apr 30, 2010 at 06:33, Dan <dan.aves_at_blackrock.com> wrote:
>> The main advantage of svn is that it only talks to the server when it has to. In order to do what you suggest and keep it up to date svn would have to constantly poll the server with "are there any locked files..." in order to show a status of locked in repo. If TSVN does get a feature to do that... please make it OFF by default.
>>
>> BOb
>
>
> Hi BOb,
>
> Agreed - that solution would be rubbish.
>
> BUT, requesting the status of a file as soon as the modify event is issued in a dev environment (i.e. developer starts changing file) & warning the user that this is locked before they do too much work would be a great compromise.
>
> No polling & very little overhead in terms of traffic - only runs a check when a file starts being modified.
>
> I know it won't happen, but it will sit on my wishlist. ;-)
Do you regularly edit files which don't have svn:needs-lock set on them?
If you set svn:needs-lock, your development environment should warn
you when you start to edit a file that's read-only (or when you
attempt to save it). That should be your indication that you need to
acquire a lock on the file, and if you're unable to get the lock, it
means someone else already has it.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2599653
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-30 13:00:24 CEST