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

Help

Home

Home » Eclipse Projects » OSEE » Keeping branches for merge to other projects/variants

Show: Today's Messages :: Show Polls :: Message Navigator

Keeping branches for merge to other projects/variants [message #780166]

Tue, 17 January 2012 09:44

Ankit Garg

Messages: 4
Registered: January 2012

Junior Member

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

Report message to a moderator

Previous Topic:	API to create Artifact Explorer
Next Topic:	How to use OSEE ATS export

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Jun 09 15:07:29 GMT 2023

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter