Josh Boyer [off-list ref] writes:
On Tue, Sep 22, 2015 at 2:40 PM, Konstantin Khomoutov
...
quoted
Hence, given any particular commit, you're able to trace all of its
ancestry, but the reverse is not possible.
That makes sense. I suppose I will have to resort to parsing output
of git-rev-list or something. Thanks for the reminder.
I think Konstantin explained why it fundamentally does not make
sense to ask "which one is the Nth one after the root". I am not
sure how running rev-list and count its output would help, unless
you are now solving a different problem (perhaps "find all the ones
that are Nth after some root", which does have an answer).