Stefan Küng <tortoisesvn@gmail.com> writes:
> Not quite: we're talking about the Subversion *library* here. And a
> client doesn't necessarily know whether the library has a workaround
> (it usually has (log --limit), but not always (locking)). That's what
> the third state would be for: if the library has a workaround, it
> would change the state from 'notsupported' to 'partlysupported'.
>
> The client can then decide on that state what to do.
Ah, I understand, thanks. I'm not opposed, but I can't volunteer to
do this for 1.5, unfortunately...
In the meantime, there is a meta-workaround. It's sort of a burden
for clients, I realize, but they could still check the capability
using the RA layer, and then display the appropriate warning or choice
to the user, using simply "a priori" knowledge of what features have
client-side-only slow support (e.g., depth). It's not ideal for that
knowledge to need to be encoded in each client, but it is doable,
until we get the above feature.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 22 20:12:16 2007