Annotate policies

[Stefan Monnier]

>> I think ultimately the question "why is this line like this?" needs more
>> than a one word (one revid) answer.  I think I'd like to conceptually get
>> the highlighted parts of the revision graph showing how that line got to
>> where it finally ended up, whether that is by its original addition,
>> merges, conflict resolution, etc, and maybe even being to jump over
>> sections where it was added and then replaced.  I don't

> That's an interesting idea, and certainly something that I would
> have liked to use last night, as "viz" and left-parent diffs were
> confusing me.

For what it's worth, I personally don't care much for annotate: I use it
fairly often, but it doesn't give the info I want.  The info I really
want is what I'd expect from "bzr diff-with-log FILE:NN-MM", which would
give me a combination of "bzr log" and "bzr diff" showing a history of
hunks (along with their commit-log) that resulted in the lines NN to MM
in FILE.

So currently, I get it piecemeal by jumping around between `annotate'
to find a revno which I tend pass to diff, log, and annotate, and
loop again.


        Stefan