On Mon, 15 May 2006, Marco Costalba wrote: > > $ git-rev-list --topo-order --after="Apr 10" --before="Apr 11" HEAD |wc > 14 14 574 > $ git-rev-list --topo-order --boundary --after="Apr 10" --before="Apr > 11" HEAD |wc > 18 18 742 > > Boundary revisions in this case are _not_ passed through search > filtering. Using --boundary option we get revisions ouside given > filter range. Right. And the commit counting is a special filter, and "boundary" is special in that it doesn't normally honor some other filters (it _does_ honor path-based ones, though, I think). So you really should see "--boundary" as a heuristic, and as a hack to help you close the loop on uninteresting commits _faster_. But if something else has closed it for other reasons, you shouldn't depend on it. Linus - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html