What loggerhead needs from Bazaar

[John Arbash Meinel]

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

Jonathan Lange wrote:
| On Thu, May 29, 2008 at 2:01 PM, Michael Hudson
| <michael.hudson at canonical.com> wrote:
|> Currently, loggerhead caches a bunch of information about a branch the first
|> time it looks at it -- roughly speaking, the merged sorted revision graph.
|>  This involved calling get_revision_graph, unsurprisingly.  Now that
|> get_revision_graph is gone, probably the pragmatic thing to do is fake it --
|> copying the _old_get_graph from bzr.dev into loggerhead.
|>
|
| What specifically do you need to get_revision_graph for? Is it
| possible that other APIs could fill the same need?
|
| jml
|
|

At the moment loggerhead does all the work that 'log' does. And dotted revnos
and merge_sorted (in general) requires the whole revision graph.

At the moment, 'bzr log' just uses a workaround for get_revision_graph. It does
dict(graph.iter_ancestry(branch.revision_history()))  (because it already has
the revision history for some other operation).

John
=:->

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

iEYEARECAAYFAkhDPpoACgkQJdeBCYSNAAO6GwCgzBL1Vi1d/UYoVuCuYHQGiEZQ
Bb0AnjjmxKgfULG3c0pid6zL9tbi1sOW
=YP1b
-----END PGP SIGNATURE-----