On Sun, 17 Apr 2005, Daniel Barkalow wrote:
> > But if there are simple helper functions to get the "next backwards in
> > time" case (by looking at the parent dates in a merge), then that should
> > be ok to do incrementally.
> Haven't written that yet, but I can do so.
Okay, I wrote this. I now have a merge-base that will find the most recent
ancestor while never looking at any parents of any commit older than the
answer. (But I'll let the previous stuff get reviewed first)
*This .sig left intentionally blank*
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html