Equivalent to svn switch?
Accepted answer
1) You can load one workspace over another. Any shared content will remain in place but any new content will be loaded
2) You can suspend one or more change sets. This removes the change set from your workspace and places it in your suspended list. You can then later resume the change set(s).
We tend to use 2) quite a bit as part of our development work flow.
Comments
Could you please provide the steps to do this or point me to the doc that describes how?
I tried something ( see below ) and it a.) seemed a bit involved and b.) resulted in my having outgoing changes even though I did expect to have any.
Here is what I tried
1.) had workspace created from stream X
2.) Made sure all my changes were delivered
3.) Open workspace definition and changed flow target to be stream Y
4.) Refresh pending changes view
I expected to only see incoming changes. However I saw outgoing as well.
That means that you had changes in your workspace that were not in the new flow target (i.e. your remote workspace is really just a personal stream. Changing the flow target doesn't change the contents of your stream. It only does a comparison with the target to show you the difference). When this happens, you have two options:
1) If those changes should be in the target, you can deliver them
2) If you don;t want those changes in the target, you can discard them or, if you just want to sync up with the flow target, you can choose Replace With/Latest from <Stream> and the component in your remote workspace will them match what is in the flow target.
Here is a link on how to suspend change sets:
https://www.ibm.com/support/knowledgecenter/SSCP65_6.0.4/com.ibm.team.concert.dotnet.doc/topics/t_suspending_change_sets.html