New idea in consultation with Dave, written by Mark Jongeling:
I would like to be able to stash any changes I made to a branch similar to how Git does it: Git - git-stash Documentation (git-scm.com)
One way of achiving this is an additional option in the Revert branch task with which I can indicate that I want to revert my branch to a point in time, and that the current state of the branch is stored, or Stashed; for example as a new branch. This new branch is in essence a copy of my branch with all the changes, then after that branch is created, reverting my original branch to the indicated point in time. That will leave me with two branches; the original one which is reverted and the stashed one which has all of the changes I originally made.
At a later time, I can then merge the stashed branch into my original branch, effectively applying my changes again.
Old idea:
Hide contentShow content
Long story short, I'd like to be able to set the origin model version during the creation of a merge sesion.
Casus:
Let's say I have a branch A. I've made some development during the period X->Y. Let's say I want to park my changes by creating a branch B and reverting branch A to timestamp X.
Then, when I eventually want to merge branch B into A, the merge session wrongly assumes that all my changes are deleted in branch A, because branch A is relatively in the past to branch B. So we want to have both model A and B to have a same base origin model version for the merge. That way, the merge sees the delta actions for branch B as additions from B->A instead of A->B.
