Re: Walking Merge History

"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.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 14 05:14:18 2007