This is exactly the issue that I haven't found a satisfactory solution for.
What I wanted to do is to allow somebody to "automatically" steal a lock
when it appears that they had the file in the local working copy.
Currently, subversion doesn't store any information regarding where a lock
came from. However, the lock command does take an optional comment. Using
this capability, we can add information into the lock comment which
indicates where a lock came from: hostname, working dir, etc.
When attempting to determine whether it is OK to steal this lock, you can
run 'svn info' on the object in question and get the contents of the lock
comment from the repository.
-Steve
On 2/26/07 3:32 PM, "Miller, Eric" <Eric.Miller@amd.com> wrote:
>> I know you can fake it by using a clean .svn file from an update:
>>
>> mv test test_obs
>> svn up test
>> mv test/.svn test_obs
>> rm -rf test
>> mv test_obs test
>> (delete missing, add unversioned)
>> svn ci -m 'ugh' test
>
> Actually I just realized that this 'workaround' loses working copy lock
> information.
>
> If a file in the original directory had a lock the update will not bring
> that lock information back (not that I expect it to!) and you must force
> a relock.
>
> Yuck.
>
> Eric
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 26 21:51:08 2007