Johannes Schindelin <johannes.schinde...@gmx.de> writes:

>> If tbdiff were "Thomas's branch diff", I would call this jbdiff ;-)
>> but I think the 't' in there stands for "topic", not "Thomas's".
>> 
>> How about "git topic-diff"?
>
> Or `git topic-branch-diff`?

Yeah something along that line, which is about comparing each step
in two iterations of a single topic.  It would be wonderful if it
also supported a short-hand

        $ git tbdiff --reflog 1.day.ago js/branch-diff

that turned into:

        $ git tbdiff js/branch-diff..js/branch-diff@{1.day.ago} \
                        js/branch-diff@{1.day.ago}..js/branch-diff

That compares "what was on the topic a day ago" with "what is new on
the topic since that time", which is exactly what an individual
contributor wants when reviewing how the topic was polished, I would
say.


[Footnote]

A variant I often use when accepting a rerolled series is

        $ git checkout js/branch-diff
        $ git checkout master...
        $ git am ./+js-branch-diff-v2
        $ git tbdiff ..@{-1} @{-1}..

so this is not only for individual contributors but also helps
integrators.

Reply via email to