RE: unneccessary diffs with $Header$

[Jim.Hyslop]

Johann Uhrmann wrote:
> there is a strange behaviour in the WinCVS command line client
> (WinCVS 1.10.8):
> 
> If I use the command "cvs admin -sRel" to mark files as "Released",
> the WinCVS client get a "Local Modified" message. It seems that cvs
> thinks the windows clients changed the text in the header tag back
> from "Rel" to "Exp".
> 
> Therefore, if a "cvs admin -sRel" is issued, all windows clients
> think that their file state is "Locally modified" instead of 
> "Up to date".
*All* windows clients? Be careful with your generalizations, please. The GNU
command-line client and SmartCVS both show the file as "up-to-date". The GNU
command-line client even shows no difference, i.e. 'cvs di' returns nothing
(SmartCVS, OTOH, flags the line as changed).

> In my oppinion, a state change should not be reflected as a change.
> (Eclipse seems to handle it that way, btw.)
This is a problem with WinCVS, not with the command-line client.

> Is there something I can change at the cvs server side?
> Is this a bug in WinCVS?
It would seem so.

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.com/experts)