Re: Reachability lists in git

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 18, 2014, 20:13 UTC
Message-ID: <xmqqzjbouv0y.fsf@gitster.dls.corp.google.com>
In-Reply-To: <20141118194129.GI6527@google.com>

Jonathan Nieder <jrnieder@gmail.com> writes:

> --ancestry-path is my current favorite tool for walking-forward needs.

Curious.  I often want to answer this question:

    Commit 982ac87 was reported to be faulty.  What topic was it on
    and at which point was it merged to 'master'?

     - What is the 'bottom' of the topic, that is, the commit
       reachable from the faulty commit that was already on 'master'
       when the faulty commit was written the first time?

     - What is the 'top' of the topic, that is, were there more
       commits made on top to build on the faulty commit on the
       topic before the whole thing was merged to 'master'?

     - Were there follow-up fixes and enhancements on the topic
       after the topic was merged to 'master' (this is harder)?

And my experiments with --ancestry-path has been less than ideal.