Any operation that modifies change history, including resume, accept, deliver, and discard, can create a gap. If you have multiple outgoing change sets in your workspace and try to deliver a subset of them that does not constitute a complete change history for any of the files they contain, the deliver fails and you are prompted to include the other change sets.
When you try to accept a change set from a source that is not one of your workspace's normal flow targets (from a work item, for example, or perhaps another workspace), that change set might depend on other change sets that are not in your workspace. Because those dependencies have not been met, there is a gap in the component's change history that can only be resolved by finding the missing change sets and accepting them in the proper order, or by accepting a change as a Rational Team Concert source control patch.
When you resolve a gap by accepting a change as a Rational Team Concert source control patch, Rational Team Concert source control creates a patch that, when merged into your workspace, modifies the files in your workspace in the same way that the incoming change set would have, but without the changes that occurred during the gap. This operation usually works automatically, but in some cases you might have to merge parts of the patch manually. For more information, see Creating and applying a Rational Team Concert source control patch.
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug