On 8/14/2011 4:13 PM, Jelmer Vernooij wrote:
> Public bug reported:
>
> Working in git working trees is reasonably quick, but a lot of
> operations require a revision number - which requires full revision
> graph access.
>
> It would be nice if there was a cache of some sort to help with
> this.
>
> ** Affects: bzr-git Importance: Medium Status: Triaged
>
You might poke at bzr-history-db which caches graphs & revision numbers
in interesting ways.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/14/2011 4:13 PM, Jelmer Vernooij wrote:
> Public bug reported:
>
> Working in git working trees is reasonably quick, but a lot of
> operations require a revision number - which requires full revision
> graph access.
>
> It would be nice if there was a cache of some sort to help with
> this.
>
> ** Affects: bzr-git Importance: Medium Status: Triaged
>
You might poke at bzr-history-db which caches graphs & revision numbers
in interesting ways.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
I1pEACgkQJdeBCY SNAAPhQwCeOX5Id cxCsdjmyuAnwu4Z SVA5 DVo2Z0l6SEuEQU4 Xd
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAk5
6n4AoIhkwqNj27h
=5WEg
-----END PGP SIGNATURE-----