[ros-dev] Re: locking files for the audit.

[Ged Murphy]

Ged Murphy wrote:
>
> Ok, slight change of plan as per option 1. It definitely is much 
> easier to lock everything at once and then unlock the code which has 
> passed.
> I'm in the process of locking now via the user 'audit'
>
> Once this is done ( about 1 hour), the method above applies to unlock 
> the code. All devs will have the ability to 'break a lock'
>
> Ged.
>

ok, everything should be locked now, with the exception of   include,  
ntoskrnl/include , media,   modules,   regtests

I've just tried unlocking rbuild and explorer with my own user account 
and it worked fine.
However it appears the lock must be broken before the svn:needs-lock 
property is removed.

For completeness, here is the method once again:

- Right click on the file / directory you want to unlock, navigate to 
tortoiseSVN and select 'check for modifications'
- Select the file(s) you want to unlock, right click and select 'break 
the lock'. SVN will automatically contact the repo and unlock the files.
- Remove the svn:needs-lock property from the files and commit to ensure 
they are no longer checked out as read only.

Happy auditing....

Regards,
Ged.