Keith Hill

The output I'm getting from this command doesn't make sense to me:

C:\Tfs\Acme> tf hist . /r /v:L3.0_REL~T /i

It is outputting history from a year ago when we applied the label to our release just a few weeks ago. What's the best way to find out what checkins have occurred since a release I'd rather not have to use a date or changeset because those are frankly much harder to remember than a label.



Re: Team Foundation Server - Version Control Odd output from tf hist using a label in version spec

Eugene Zakhareyev

There is label comparison feature in Labels Sidekick that allows you to compare two labels or label and the latest version.

Hope that helps, Eugene






Re: Team Foundation Server - Version Control Odd output from tf hist using a label in version spec

Keith Hill

Thanks for the pointer. So is the tf hist on a label behavior expected or is it a bug (or limitation)



Re: Team Foundation Server - Version Control Odd output from tf hist using a label in version spec

Eugene Zakhareyev

Keith, I played around with the command a bit - you do get expected behavior when the command is performed on single file. When you perform the history on the folder, it will also include the changeset for the folder(s), which may not be the expected output.

For example, say I have the following setup: there is $\Project\Folder under which there is file File1.cs; let's say I have labeled the revision 100 in label, and the latest is 200.

When performing "tf history $/Project/Folder/File1.cs /r /v:LLabel1~T /i" the output will be as expected, changeset 200 will be displayed.

However, when "tf history $/Project/Folder /r /v:LLabel1~T /i" is performed, you will have in addition the changeset 50 (which in my case where the folder item "Folder" itself was created)

So I think the folders in your path and recursive flag accounts for extra changesets appearing.

Cheers, Eugene