Tree-Based Rollbacks

[d4l3k]

Every patch has a unique id and a parent patch. When someone rolls back to a specific patch, and then starts modifying things the rollback point then has two child patches. This is similar to forking, except there is no merge (which potentially could be implemented). There would be a graphical tree where you could switch the document to any of the patches on the tree and then set that to be the live one. The interface would probably be a sidebar on the right that would easily allow you to both view the document and the tree.