Version history behaviors

[auniverseaway]

1. If you copy, the copy gets fresh history.
2. If you copy to replace, the copy inherits the replaced history.
3. If you move, the history moves with it.

From @bosschaert: 1 & 3 are already the behavior.

Number 2 will need to be implemented.

[bosschaert]

On 2. above, what do you mean exactly? Replacing the content of an existing document with the content of another existing document, without replacing the target document's history? Because that is exactly what you get when you simply call PUT on a /source/... URL?
In that case you just have to get the content from the original and put it in the target... da-collab is automatically invalidated in that case already too.

[bosschaert]

I worked on a prototype with @karlpauls during the AdaptTo conference last week. Plan is it finish this and create a PR.