Searching for change sets adds streams to workarea targets?
Hi,
In trying to help with understanding of why some changes made into a
stream unexpectedly, I used the "Locate change set" from the context menu in the History view. There is a means of adding other flow targets
(Components from all flow targets) which I used to point the search to additional streams. That helped me find the baseline that was causing the confusion. However, after that search is done the workspace' flow targets contain any of the streams that were searched ?!?!?
This happens in RTC 1 and RTC 2. Is that intentional ? Doesn't seem to be a good idea, especially when there is potential for cross-stream "contamination".
In trying to help with understanding of why some changes made into a
stream unexpectedly, I used the "Locate change set" from the context menu in the History view. There is a means of adding other flow targets
(Components from all flow targets) which I used to point the search to additional streams. That helped me find the baseline that was causing the confusion. However, after that search is done the workspace' flow targets contain any of the streams that were searched ?!?!?
This happens in RTC 1 and RTC 2. Is that intentional ? Doesn't seem to be a good idea, especially when there is potential for cross-stream "contamination".
One answer
It's subtle but when it says "flow targets", that is referring to the flow
table, and pressing 'Add..." modifies that table.
If you just want to check a stream without modifying your current
workspace/stream, you can select the second option "Component in another
repository workspace or stream"
On Tue, 15 Sep 2009 08:53:02 -0400, yzwkzfn
<ramerk> wrote:
--
table, and pressing 'Add..." modifies that table.
If you just want to check a stream without modifying your current
workspace/stream, you can select the second option "Component in another
repository workspace or stream"
On Tue, 15 Sep 2009 08:53:02 -0400, yzwkzfn
<ramerk> wrote:
Hi,
In trying to help with understanding of why some changes made into a
stream unexpectedly, I used the "Locate change set" from the
context menu in the History view. There is a means of adding other
flow targets
(Components from all flow targets) which I used to point the search to
additional streams. That helped me find the baseline that was
causing the confusion. However, after that search is done the
workspace' flow targets contain any of the streams that were
searched ?!?!?
This happens in RTC 1 and RTC 2. Is that intentional ? Doesn't seem
to be a good idea, especially when there is potential for
cross-stream "contamination".
--