-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Noel Yap Sent: Friday, November 14, 2003 1:22 PM To: Shelley L. Shostak Cc: jab; Steve Smythe; perforce-user at perforce.com; perforcehelp; perforceusers; cmodev; ptdev; spgtech Subject: Re: [p4] Perforce client only thinks the file is up-to-date (Was: Perforce and CVS full or delta wire transmission?)

We have had anecdotal evidence that the Perforce Client will falsely think that a file is up-to-date when, in fact, it is not. This problem occurs extremely rarely which is why I'm trying to reach as wide an audience as possible.

I think capturing the output of the following commands might give some hard evidence that this is happening: $ p4 have file $ p4 print file#version >file#version $ p4 diff file#version $ diff file file#version

The output of the last two lines should be the same. When the problem occurs, it's most likely on an unopened file so the "p4 diff" should say there's nothing different.

Perforce support, could you verify that these steps should show evidence that something is wrong -- the only thing I can think of that'll give a false negative is if the "p4 print" line will just do a cat of the file system file?

Thanks, Noel

"Shelley L. Shostak" wrote:

didn't reflect that on the server. My only recourse was to remove the file from the file system, then do a "p4 sync -f" on the file. Two other colleagues have given similar tales. Have you heard of any other occurrences of this?

evidence. Hopefully, the next time this happens, I'll have something (it's occurred about once every six months).