Can "bzr annotate" be sped up?

[John Arbash Meinel]

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

On 06/17/2011 06:51 PM, Stefan Monnier wrote:
>>> So maybe a workaround for this lot-of-revisions case can be giving
>>> annotate/qannotate a line number range to make it give answers faster
>>> for the lines Eli cares about.
> 
>> Yes, that would be very good, as normally I need to annotate only a
>> very small portion of a file.
> 
> Yes, yes, yes.  At the risk of repeating myself, here's how I see it
> working:
> 
>    "bzr log --show-diff --line-range NN..MM FILE"
> 
> After all, I don't care about the "annotate output".  All I want is to
> find the sequence of diff-hunks (and corresponding commit-logs) that
> resulted in lines NN..MM of FILE.
> 
> Currently, to get that info I end up having to run "bzr annotate"+"bzr
> log --diff" X times (where X is the number of hunks that affected the
> lines I care about between the introduction of the problem I'm
> investigating and the branch tip), which is *dog slow*.
> 
> 
>         Stefan
> 
> 

bzr qannotate does all of that for you...

And I believe 'bzr gannotate' had a 'back' button that would look at the
line you are on, find its revision, and then go to the parent of that
revision. qannotate does it differently, I believe. It has the history
graph in the bottom left, and when you select a line, it will
auto-select the entry in the graph, and then you can double click on an
ancestor to load its version.

John
=:->

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

iEYEARECAAYFAk37h04ACgkQJdeBCYSNAAM/5wCguIxk0BeWIK+VjmlZPyPwPlVl
N7sAmwWhNF/s6Bl8FOlLZ7hqTdC0uMLF
=ISmO
-----END PGP SIGNATURE-----