Is it possible to view a listing of the change sets

[christian]

Hi, is there anyway of getting to a list of changes sets (a check-in of one or more items as a single transaction) that have been performed against a repository? Even better, can I then drill into one of these change sets to see what items were modified? Better still can I then do a diff on the before and after image of these items so that I can review what actually code was changed?

If not, I think this would be pretty high on my wish list as a new feature. It looks to me that you guys are right on the ball with the idea of change sets as they often provide a better / right level of granularity for tracking within version control rather than at the individual file level.

Thanks
Christian

[ericsink]

Hi, is there anyway of getting to a list of changes sets (a check-in of one or more items as a single transaction) that have been performed against a repository? Even better, can I then drill into one of these change sets to see what items were modified? Better still can I then do a diff on the before and after image of these items so that I can review what actually code was changed?

If not, I think this would be pretty high on my wish list as a new feature. It looks to me that you guys are right on the ball with the idea of change sets as they often provide a better / right level of granularity for tracking within version control rather than at the individual file level.

Thanks
Christian

Yes. When you invoke Show History on a folder, you will get a dialog. Choose the radio button that says

View folder history by version

This will show all of the changesets for that folder. Double-click on one to see the details behind it.

[christian]

That's excellent Eric. I assume that selecting an individual folder, you'll only see those change sets that affected that folder (and its children). Then drilling into one of these entries you’d be presented only with those items in the change set that affected that folder (recursive)?

So if a change set included operations that touched two sibling folders (say $Mainline/foo and $Mainline/bar) then viewing the change sets for $Mainline/foo you'd see the entry for the change you've just made, drilling into this entry you'd see only that action that affected $Mainline/foo and NOT the other action that touched $Mainline/bar.

So to really get to a “repository view” of the change sets for Mainline (read active development code line) and to see what was included in each you would go to $Mainline and view history by version. You'd see an entry for the change we’ve made that upon drill down includes actions for the two sibling folders.

Couple of observations that I believe may be repeating what others have already posted:

When you drill into an individual change set, the items you are presented with are missing their path in the repository.
It would be great if you could select an item and do a diff on the before and after image of the items listed directly from this drill down menu.

Thanks
Christian

[ericsink]

Then drilling into one of these entries you’d be presented only with those items in the change set that affected that folder (recursive)?

Actually, no. I just checked -- when you double-click to drill down, you get all the items in that changeset, repository-wide. I think I like the fact that it works this way, but I'm not 100% sure.

When you drill into an individual change set, the items you are presented with are missing their path in the repository.

Yeah, it would be better if the path was there.

It would be great if you could select an item and do a diff on the before and after image of the items listed directly from this drill down menu.

Also a good suggestion.

[christian]

Actually, no. I just checked -- when you double-click to drill down, you get all the items in that changeset, repository-wide. I think I like the fact that it works this way, but I'm not 100% sure.

Tried to test this myself but I was having some problems in getting the client to display the list of change sets when viewing a folder by version. The grid was showing a whole series of blank rows even though I was getting a "Query result" greater than 0 at the bottom left screen.

Selecting one of these blank lines I get the option to view its content which I do and get an "Object reference not set..." error which I believe is an error due to be fixed in vs 3. I'm using vs 2.0.6 against the demo server.

As to whether you should see all the actions in the change set or just those that relate to the folder you're querying... Yeah, I agree I think on balance I prefer to see the lot of them.

Regards
Christian