Annotate policies

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Monnier wrote:
|>> 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
|
|
|

Have you tried using 'gannotate'? you can double click to show the diff, and see
the log comment in the bottom. Seems to be a good fit for what you are doing.
But yes, it is a gtk gui if that prevents it from being used.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhG0VIACgkQJdeBCYSNAAM9ugCdHDWRHAyG4ifgF5h5X1hor3yG
PrYAn1V8dN3nAM3ZHUsZt6HySWYb/RGk
=88WL
-----END PGP SIGNATURE-----