file ancestors

[Johan Rydberg]

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

John A Meinel <john at arbash-meinel.com> writes:

>> Regarding building full branch graphs:
>> 
>> Right now revision_graph reads _every_ revision to get parent
>> information.  This is quite expensive, esp with a remote revision
>> store.  Maybe this information could be cached in a "revision-graph"
>> file in ".bzr" directory.  The format could be simple:
>
> Actually, we already have that information. It is in the table of
> contents for the inventory.weave file.

Yes, I know that.  But on my computer it takes ~15 seconds to generate
the graph, which I think is a bit too long for a "bzr log FILE" --
those little operations should be _instant_.  I have not yet tried to
implement my proposed format, but I'm quite sure it is faster to read
and parse than an weave file that is over 2MB.

>>    REVISION-ID:PARENT[,PARENT[,...]]
>> 
>> If there is no entry for a revision in the file, it should be treated
>> as a ghost revision.  

~j
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDg5iy3CqIy3K3X2ERAnAFAKDSQISh+DwLegwT/47iAPO4ahAheACfYz4M
pIBLZ6t4ZzQflRryVizzWHA=
=3b1c
-----END PGP SIGNATURE-----