On May 1, 2005, at 1:29 AM, SteveKing wrote:
> Ben Collins-Sussman wrote:
>
>> If you don't implement this, then TSVN users will have no way of
>> discovering other people's locks. That seems like a really
>> fundamental thing, not something I would expect a commandline client
>> to do and a GUI *not* to do (especially since TSVN users are much
>> more likely to use the locking feature!). So it's definitely worth
>> trying.
>
> That's not exactly true. TSVN users *can* see other peoples locks,
> just not in the repo browser. That information is available in the
> "check for modifications" dialog which basically does an 'svn st' and
> an 'svn st -u' if requested. There, other people's locks can be seen.
>
Aha, good point. So then the commandline client and TSVN would be
equal in this feature -- both browsing remote locks via 'status -u'.
Perhaps in 1.3, we can improve svn_client_ls() as you suggested, and
then both TSVN's repository browser and 'svn ls -v' would show remote
locks.
Anyway, it would be nice to know exactly how big the performance hit
is... it would be nice if you tried to show locks in ther repos
browser, just to see.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 1 15:42:47 2005