brainstorming - what to do with annotations

[Andrew Cowie]

On Mon, 2007-09-10 at 13:14 +0100, Michael Hudson wrote:
> I'm not sure what the consequences of not storing annotations at commit
> time are.  Could they be computed later and still cached?

Only generating the annotation data on [first] request would certainly
be a more traditional approach to the caching problem.

I imagine it would hinge on whether or not you have write access to the
branch so you could cache the annotation data if necessary. Although I
might suggest that running annotate on a remote branch (vice cloning it
locally and running annotate on that) is a bit silly, I can see that
being a worry.

Possible rebuttals to that are "use the cached data if it exists,
otherwise, too bad, generate it, and cache it if you can. If you can't,
too bad" and "maybe cache the annotation data somewhere else, not in
that branch's .bzr"

Incidentally, darcsweb took the "generate requests on first request and
cache" approach (although this was outside the branch it was reporting
on, not in it).

AfC
Sydney

-- 
Andrew Frederick Cowie
Managing Director
Operational Dynamics Consulting, Pty Ltd

Sydney    +61 2 9977 6866
New York  +1 646 472 5054
Toronto   +1 647 477 5603
London    +44 207 1019201

We are an operations engineering consultancy focusing on strategy,
organizational architecture, systems review, and change management
procedures: enabling successful use of open source in mission
critical enterprises, worldwide.

http://www.operationaldynamics.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070910/98d1191d/attachment.pgp