Hello, Shawn O. Pearce wrote: > $ git rev-list v1.5.0-rc0..next | wc -l > 687 > $ git rev-list v1.4.4.4..next | wc -l > 1051 > > So what about doing Junio's suggestion of going by topology and > coming up with the possible set of tags (v1.5.0-rc0 and v1.4.4.4 > right now), and if more than one is found compute the number of > commits between each tag and the requested revision, and take the > tag that has a smallest number of commits? One scenario where this will fail is when a bugfix is commited on top of v1.4.4.4 and then is merged into v1.5.0-rc0+gabcdef. Just my 0.02$. Uwe -- Uwe Kleine-König exit vi, lesson III: : x ! <CR> NB: may write current file - 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