What should happen when reverting revisions?

Problem/Motivation

When reverting a node revision in Drupal via the UI it actually creates a new revision, just with the same data as the revision you're reverting to. How should this work in respect to replication?

- Should the revision created have the same revision UUID (revision hash) as the revision reverted to?
- Should the revision have the same parent has the revision reverted to?
- If yes to both of the above, wouldn't this cause a conflict?
- What happens to the revision tree, would it become out of sync with the upstream?

Proposed resolution

- Write a test!

Remaining tasks

User interface changes

API changes

Data model changes