Eclipse Community Forums: OSEE » ANSWERED: Keeping branches for merge to other projects/variants

Home » Eclipse Projects » OSEE » ANSWERED: Keeping branches for merge to other projects/variants(Is it possible to prevent a branch disappearing when it has been merged to its parent? - Yes)

ANSWERED: Keeping branches for merge to other projects/variants [message #487879]

Thu, 24 September 2009 12:27

Eclipse User

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"?

[Updated on: Tue, 30 March 2010 10:43] by Moderator

Re: Keeping branches for merge to other projects/variants [message #512555 is a reply to message #487879]

Fri, 05 February 2010 08:35

Eclipse User

This feature was added subsequent to OSEE 0.7.0 for which the question was posted.

Comitted branches remain visible in OSEE 0.9.x and can be archived on request.

Re: Keeping branches for merge to other projects/variants [message #576252 is a reply to message #487879]

Fri, 05 February 2010 08:35

Eclipse User

This feature was added subsequent to OSEE 0.7.0 for which the question was posted.

Comitted branches remain visible in OSEE 0.9.x and can be archived on request.

Previous Topic:	New Install with 0.8.3
Next Topic:	Starting state for a Wokflow Configuration - can it be changed?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 03:22:01 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter