No need for revision comments in code
With the release of Visual Studio 2008 and TFS 2008, there is now even less of a reason to place any revision comments in the code base. Once upon a time all reputable source control systems had a keyword expansion feature that included the revision comments for all revisions in the source file.
Version control managers de-emphasize this feature because users should use the repository for getting comments, which is tooling accessible and if readers rely on the code base for the revision comments, developers are less likely to provide good revision comments.
The keywords feature is totally removed from TFS. I think this is a mistake (though welcome because keyword support is a pain). I have heard that there are some compliance requirements that comments for code changes must appear in the code base. Of course the requirement itself is from the dark ages, but nonetheless, it should be supported.
Apart from those that must support the above requirement, some development teams prefer inline revision comments (i.e., // RKK 03/02/98: Fixed bug 2937 ) so that they know that a certain area of code has been "touched," since, as we all know, fixing one bug begets another and finding who touched a line of code in a version control system usually requires a binary search of diff'ing to find the offender.
TFS 2008 and VS2008 fix this problem. The new annotations feature permits one to easily see exactly who updated each line of code with a quick link to revision comments.
This feature has been provided with the TFS Power Tools for a while now. However with its integration into the IDE, it is a simple case for version control managers to make to prohibit the use of file header and inline revision comments.