Speedup with history-db

[John Arbash Meinel]

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


...
> 
> Fair enough.  The only use cases that really bothers me is this
> 
>     bzr log --include-merges -c REVISION
> 
> This is something I do quite a lot, because I like to know what went
> into merge commits and people tend to not describe that adequately in
> the log message of the merge.  This command does not mention dotted
> revnos, only revisions on the mainline (I do understand that -
> --include-merges is a reference to dotted revnos in disguise).  The
> output of the above command must be accurate, otherwise I will be
> forced to use --no-plugins, because I cannot trust the output.  It
> would be nice if it could be fast as well, but accuracy is more
> important.
> 
> Thanks.

That still works. The example that fails is:

 bzr log -rDO.TT.ED..X

- -c X will always use 2 mainline revisions.

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

iEYEARECAAYFAk3k+lsACgkQJdeBCYSNAAP63gCginjM6HioBCbJuxR0WZa/94Nh
TVYAn327MDecsPwOnug9AKUZXdwr4Mzg
=dXxg
-----END PGP SIGNATURE-----