What if nothing committed on Pending Change Set

[gckoch]

Re Vault 5.0.1 (18729), I noticed after some length of use that the Pending Change Set panel is full of "uncommitted" stuff. Meanwhile. I have merged, branched, and modified 1000s of files.

Linda, What if I never commit?

I can see that obviously sometimes when I check in a file Vault forces me to uncheck an uncommitted file which blocks my check in. It seems to have no affect on diffing, mergining, branching, and the _current state_ of a file.

Is the purpose of committing merely to log entries in a log view like Pending Change Set? to allow you to edit comments, shelve it? Otherwise, it just blocks you temporarily from checking in a file. Thanks, Greg

[lbauer]

What if I never commit?

The pending change set keeps track of Vault operations that have not yet been committed (checked in) to the repository. If you never commit a transaction in the pending change set, it sits there until you undo it or clear your client-side cache. If there are duplicate or conflicting transactions in the pending change set, you'll get an error message.

You can undo a transaction by right-clicking the item in the Pending Change set, and select Undo. This will remove it from the Pending Change Set. You can select several items at once to make this easier.

Here's some information about clearing the client-side cache:

http://support.sourcegear.com/viewtopic ... 13&t=11513

Checked out files will still be in the pending change set after this, since they haven't been committed or checked in yet.