Re: Walking Merge History

Karl Fogel wrote:
> "Hyrum K. Wright" <hyrum_wright@mail.utexas.edu> writes:
>> Sounds good. The plan will be: call found_ancestor() on any interesting
>> ancestor, and then potentially call any of the other callbacks to
>> indicate that something else (branch, copy, merge) happened.
>>
>> Of course, a consumer can leave any of the callbacks as NULL, and the
>> walker will ignore them.
>
> Yup. I guess each callback has to have its own '*stop' flag, but
> there's no way to avoid that, I think.

Actually, we have precedent already for a different stop mechanism:
the error SVN_ERR_CEASE_INVOCATION. Yes, it's an error creation from a pool
and all that, but I seriously doubt we're talking about noticeable cost.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand