|Keeping branches for merge to other projects/variants [message #575696]
||Thu, 24 September 2009 16:27
| Mark D-B
Registered: July 2009
Normally, it makes sense for a branch to disappear when it has been committed to its parent.|
However, what about the situation where there are several variants of the same system?
We do some work for variant "x" and this needs to be committed to it. However, the work may be used for variant "y" as well but we don't know for sure yet.
We can't cross-merge to "y" because we may decide not to use it in "y", but the branch for the work is going to disappear when it is merged to its parent "x".
Is there a way to stop the sub-branch disappearing when committed, or is the only solution to cross-merge to a new branch under "y" first before committing to "x"?
Powered by FUDForum
. Page generated in 0.04117 seconds