You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2018. It is now read-only.
The pull request fedwiki/wiki-client#52 brings drag-and-drop merging of divergent pages possible by simply consolidating the divergent journals and replaying the result. This raises the question, how should journals be combined?
The obvious choice would be to interleave actions based on dates. In my prototyping I stopped short of this because I knew dates could be wrong or even missing. It is possible to infer missing dates and the inference could have bounds based on surrounding actions. But better to try something simpler first.
Since I use a drag gesture to request the merge, I chose to add the dragged journal actions to the end of the journal upon which they were dropped (omitting duplicates, of course). This makes the merged result dependent of which way the merge was requested. If you don't like the merge, you have another way to try it. If you have three divergent pages you have many things to try.
It is possible with this simple approach to do much more delicate merges: pick earlier versions of A and B, merge them, then merge the rest of the actions in some other order.
A disadvantage of the simple approach is that dates in the journal can be out of order. Is this bad? It would seem so but what makes us think chronology is important when work has been done independently?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The pull request fedwiki/wiki-client#52 brings drag-and-drop merging of divergent pages possible by simply consolidating the divergent journals and replaying the result. This raises the question, how should journals be combined?
The obvious choice would be to interleave actions based on dates. In my prototyping I stopped short of this because I knew dates could be wrong or even missing. It is possible to infer missing dates and the inference could have bounds based on surrounding actions. But better to try something simpler first.
Since I use a drag gesture to request the merge, I chose to add the dragged journal actions to the end of the journal upon which they were dropped (omitting duplicates, of course). This makes the merged result dependent of which way the merge was requested. If you don't like the merge, you have another way to try it. If you have three divergent pages you have many things to try.
It is possible with this simple approach to do much more delicate merges: pick earlier versions of A and B, merge them, then merge the rest of the actions in some other order.
A disadvantage of the simple approach is that dates in the journal can be out of order. Is this bad? It would seem so but what makes us think chronology is important when work has been done independently?
The text was updated successfully, but these errors were encountered: