Well, after listening to this thread for a while, I thought I would weigh in. I don't want $Log$ and my developers mostly don't know or care about it. As it is, I have trouble getting my developers to put in comments. If they then got their files polluted by those comments, they would put even fewer comments.

Also, it is difficult enough to get people to integrate on a regular basis without adding more confusion to the mix by putting in somewhat extraneous differences in all those files. Please correct me if I am mistaken, but if we had $Log$ expansion, all files would have conflicts during branch to branch integration where the expansion had occurred.

Yes, I could just not use $Log$, which is what would happen. However, there are a few jokers in the mix at my company that would try it out because it was new. I would rather not have to go and politely chastise people for use of another feature of perforce.

Finally, I would rather perforce work on the bugfixes and new features of my choice (a true RENAME!) than a feature that will cause me problems.

Ines Paul Goffin wrote: