getting the inventory of a revision, or, Why doesn't the API look like I think it should?

[Jamie Wilkinson]

This one time, at band camp, Aaron Bentley wrote:
>Jamie Wilkinson wrote:
>
>>  * You get the tree from the branch!  Oh, don't need to get the revision
>>    now.
>>
>>  * Examine the inventory from the tree given.
>
>Actually, you can get the inventory directly from the branch, too.
>
>In terms of the logical construction, you do have the containment right.
>That is, a branch refers to a series of revisions, revisions consist of
>metadata and a tree, a tree consists of an inventory and file contents
>
>I should note that we're in the middle of splitting Repository out of
>Branch.  Branch's main responsibility then becomes the history list.
>
>Repository is in responsible for all revision data: revisions,
>signatures, inventories, and file contents.
>
>On one hand,
>
>for (branch.get_inventory(r) for r in branch.revision_history())
>
>doesn't seem all that bad to me.
>
>But my gut instinct is that you're wanting a layer that doesn't exist
>yet-- a fascade meant to simplify life for external library users.

Yeah, I guess that's it :)

Thanks for the summary.