Stale changes

[grs]

Somehow, one of my working folder work areas has developed some synchronization issues with respect to my repository.

If, in VS2008 or the fortress client, I execute a "check in" at the solution level, I am presented with a number of prospective changes that were either backed out, or have been previously committed to the repository. if the change is file or directory related, the entire change set fails if one of these errant changes is selected for inclusion. Is there a tool that will allow fortress to just forget about these changes (since they are largely included in the repository already)?

I would prefer not to remove and recreate this set of working directories.

Gregg Siegfried

[lbauer]

Before you do a checkin, review the items in the pending change set in the Fortress Client or in VS 2008. You can undo any "orphaned" transaction that you no longer wish to commit. Just right click on the item and select "Undo."

See this KB article for more info on "orphaned" items:

http://support.sourcegear.com/viewtopic.php?p=26479

[grs]

Thank you, Linda.

Oddly, I have no context menu nor "undo" option on the pending changes window.
Perhaps I have a misplaced configuration setting?

[lbauer]

That's strange. Could you post a screenshot of what you're seeing? Also, what version of Fortress are you using?