On Sep 14, 2007, at 2:04 PM, Erik Huelsmann wrote:
>>> I suspect that this is because the workspaces that do _not_ have the
>>> lock have no indication from the repository that locks exist. Is
>>> this
>> a
>>> correct guess?
>>
>> Yep.
>>
>>> It would be nice for
>>> the workspace to know which files have locks on them (upon "update",
>> of
>>> course), and better yet, to know who has those locks.
>>
>> I agree, this would be quite useful. Locking has always seemed like
>> such an afterthought and really doesn't get a lot of attention.
>
> I can't help it, but this is by design, not because locking is or was
> an afterthought: it would be really useless to have this information
> in a working copy, because the minute it's stored in the working
> copy, that information may be outdated.
>
> If you want to have up-to-date information on locks, you need to
> contact the server. That's what this 'non-availability' of information
> is about...
what command should we be using to get the list of locks from the
server?
thx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 14 23:49:12 2007