[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Walking Merge History

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-09-14 15:53:23 CEST

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

Received on Fri Sep 14 15:49:46 2007

This is an archived mail posted to the Subversion Dev mailing list.