[RFC] browsing history API

[Johan Rydberg]

Martin Pool <mbp at canonical.com> writes:

> I think you will want the entire graph of the file leading up to the
> version present in a particular tree.  Although there may be other
> irrelevant versions of that file that haven't been merged, all the ones
> that have been merged in are by definition relevant.  You can do this
> just by looking at the file's graph.
>
> (Or if not, maybe you can explain more about what you want to get out.)

What I want to get out is a (ordered) list of all revisions that
changes a file, that has been merged into a branch.

> I've been wondering if we should save for each revision a list of the
> modifified files, with some details including their file name and
> directory, and the previous revision that modified that particular file
> - essentially a structured diff between the two inventories, similar to
> what is held by a TreeDelta.  Some operations need this information,
> including log -v and files_affected.  If we include the previous
> revision then we can skip back through these records without needing to read
> every revision.

Something like the 'revision changes' concept I used in my initial
knit work?

~j