How to not have pending changeset cluttered with unmodified

[Perry]

The pending changeset is cluttered with many unmodified entries.

What I (and most users, I assume?) would like to see is the list of pending modified files.

Also, when I go to checkin, the list of files affected is too large for me to want to spend time working on, because it too is cluttered by including all the unmodified files.

Is there a way to only see the actually modified files? Surely that is by far the most important, and interesting, view?

(I did look in the Help under Check-in, but there was only one brief paragraph on checking files in.)

[dan]

Why are there so many unmodified files in the pending change set?

They should only be in the pending change set if they've been checked out or touched.

[Perry]

There are many modified files for two reasons:

- I check out everything so I can edit in disconnected mode

- I check out everything because the IDE integration doesn't work with VS.NET 2005, so it is much easier to check out everything when I'm the only person working on a project for a while


But, it isn't really very helpful to me for the tool to tell me that I checked out everything -- I know that -- what I need it to tell me is which files have changed -- and thereby, what the effects of my checkin will be.


Now, actually they are in list controls, so I've figured out that I can sort on the type to get the modified ones listed first. This mostly does take care of it - but it will still be nice if I had an option to not have to see all those unmodified files -- and not to have to re-sort every time. Is it possible this could be added to an RFE?

(I'm interested partly because I think most users will feel the same way as I do about this.)

[dan]

You might be happier using "CVS" mode, where all files are retrieved read-write, and Vault will notice when they have been edited and put just the edited files in the pending change set. See Tools->Options->Concurrent Development Style

Otherwise, using the column sorting in the pending change set is probably the best workaround.

[joshyeager]

There is an option in the Vault client to Undo Checkout on unchanged files, instead of checking them in. That way, you can just check in the whole set, and it will only do it to the modified ones.