On Tue, Sep 13, 2011 at 06:02:44AM +0300, Daniel Shahaf wrote: > The branch doesn't have code for answering questions such as > > - where were a given path's parents copied to? > - when was a given path deleted? > - (questions about merges) > - (questions about a directory's properties having changed, > as opposed to `something under that directory' having changed)
These are high-level questions that can be addressed after reintegrating the branch. I'd consider the branch done as soon as both backends store successors of each node-revision, and are able to return the list of immediate successors of a given node-revision. We must also have some basic unit tests to show that it works. At that point I'd like to merge into trunk and continue development there. > The branch doesn't have yet > > - consumers of these new APIs One other remaining item is in-place upgrades. I'd like to optionally support in-place upgrades instead of requiring users to dump/load.
