Hi, On Fri, Jun 18, 2010 at 11:40:16AM +0200, Johan Herland wrote: > [1]: To put the search in general terms: Find all merge commits that has > _both_ (or in the case of octopus; _all_) of the candidate commits (but none > of the other merges) somewhere in its ancestry. You could implement this by > first intersecting the sets returned from these commands (run in the > submodule): > > git rev-list --merges --ancestry-path --all ^B > git rev-list --merges --ancestry-path --all ^F > > to get the set of merges descending from both 'B' and 'F', and then prune > each member in the remaining set that has another set member in its > ancestry. Is the --ancestry-path option already implemented? Because on my git 1.7.1 it does not seem to. What does it do? cheers Heiko -- To unsubscribe from this list: 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