Re: [PATCH] Re: svnversion weirdness with svn:externals

Julian Foad <julianfoad@btopenworld.com> writes:

> > Ack. Scratch that. This one's cooler. It not only ignores statuses
> > after externals start getting handled -- it uses the cancellation
> > callback to trigger an immediate (or at least much-more-nearly
> > immediate) halting of the status operation after that point.
>
> This depends on the status report sending everything else before the
> externals. Is that guaranteed by its API?

It will be soon. :-)

Seriously, you've made a good point. We let our command-line client
assume too much about the internals of the client libraries with
respect to notification. We really should document the notification
ordering in our client API where it makes sense to do. A careful
client coder today would note that there are no promises about the
notification order, and likely disregard all notifications as a
result.

> Perhaps the optimisation of stopping as soon as you get the first
> external report is over-kill, as the likelihood of someone having a
> very large number of externals is low.

Honestly, I just felt like it would be cool as an example of how to
use the status, notification, and cancellation callbacks in concert.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 5 15:47:39 2003