Speedup with history-db

[Eli Zaretskii]

> Date: Tue, 31 May 2011 16:25:31 +0200
> From: John Arbash Meinel <john at arbash-meinel.com>
> CC: bazaar at lists.canonical.com
> 
> > 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.

Not with the specific revision I somehow managed to find:

   bzr log --include-merges -c104363

Several other merge-commits I tried indeed work (and are about 15
times faster with the plugin than without it).  But this single
revision 104363 causes trouble.  Could you please take a look at the
above command with that specific revision on the Emacs trunk?

Thanks.