SteveKing <steveking@gmx.ch> writes:
> So to check if I got it right this time:
> - if the svn_lock_t structure is filled in in a working copy, *that*
> working copy owns the lock.
> - if someone else has a file locked, it's not possible without
> contacting the repository to find that out (updates don't update that
> information in the wc - that's not stored in the wc at all).
That is correct.
> So now my request for an enhancement to the svn_wc_entry_t struct: a
> boolean value indicating that an entry is readonly. Since
> svn_client_status2() already opens those files to check the filedates,
> that information is 'for free'. Otherwise I have to do a filestat call
> for every file again, which is very bad (performance wise).
Could you explain again why you need to know the read-only status?
You do realize that not all files locked by (someone) have their
read-only bits set, right? TortoiseSVN being all Explorer-plugin-y
and stuff, seems that just read-only-ness (for read-only-ness's sake)
is something folks can get via other routes.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 13 20:33:10 2005