2 repository workspaces loaded, change sets going into the wrong repository workspace.
One answer
But to explain specifically what you are seeing, we'd need more information, such as:
Are these two workspaces in the same RTC repository, or different RTC repositories?
I assume the same component loaded into both sandboxes? (If not, it wouldn't make sense to "drag the change sets" from one sandbox to the other).
Are there Eclipse projects in these components, and did you tell RTC to "load Eclipse projects" (so they show up in your project explorer), or did you tell it to just load the files into the sandbox without creating Eclipse projects for them?
Comments
Are these two workspaces in the same RTC repository, or different RTC repositories?
Same repository server, each workspace is from two streams, one stream based on the other's component, I think. At least the components have the same name.
I assume the same component loaded into both sandboxes?
Are there Eclipse projects in these components,
Eclipse will not let you import two projects with the same name ... so RTC will happily load both sandboxes on disk, but Eclipse would not be willing/able to load the same Eclipse project from two different locations on disk. The next question is whether you are absolutely 100% positive that made your changes to the repo2 sandbox, and not to the repo1 sandbox? In particular, if you double click on the changes in the Unresolved folder, and then compare what it tells you with what is on disk, does the Unresolved folder tell you that a repo1 file has some new content, when in fact it does not, and the corresponding file in repo2 has that content instead?