Re: [Gnu-arch-users] Re: release goals for Bazaar 1.1

[Aaron Bentley]

Stefan Monnier wrote:
> > You might seriously want to look into fai, since it seems to have some
> > of the features that you are asking for.
>
>
> Indeed, there are several third party packages offering functionality along
> the lines of what I'd ideally want.  But I'd like to see something like that
> merged into the main application.
>
> Note also that the feature I described can be implemented without any need
> for side-info: all it needs is the {arch} patch-logs and the diffs from
> the archive.  No need to cache any kind of annotation.  You don't even need
> a revlib.  That's why I think it'd make sense to see this in Arch before
> "tla annotate".

Fai annotate just uses the {arch} patch-logs and diffs from the archive. 
 On local archives, it can be pretty quick.  On remote archives, it is 
usually damn slow.

The reason is that assembling this information requires retrieving all 
changesets for all the revisions that modified a particular file.  So 
the more changesets that modified the file, (and the higher the latency, 
and the lower the bandwidth) the slower the process.

The motivation for caching is to reduce the pain of repeatedly 
re-calculating this data every time you want to view the annotation of a 
given file.

I believe the same would be true of your "tla trace-code".

Aaron