16 messages in com.perforce.perforce-user[p4] Unwanted new timestamps after su...
FromSent OnAttachments
Max.Ritter08 Dec 2004 05:58 
Noel Yap08 Dec 2004 06:28 
Robert Cowham08 Dec 2004 07:36 
Grills, Jeff08 Dec 2004 08:15 
Noel Yap08 Dec 2004 08:19 
chri...@ni.com08 Dec 2004 08:34 
Arnt Gulbrandsen08 Dec 2004 08:48 
Ivaylo Beltchev08 Dec 2004 08:55 
chri...@ni.com08 Dec 2004 09:20 
Max.Ritter08 Dec 2004 09:32 
Kevin Wang08 Dec 2004 10:51 
Noel Yap08 Dec 2004 11:45 
Alen Ladavac09 Dec 2004 00:45 
Chuck Karish17 Dec 2004 08:16 
Max.Ritter17 Dec 2004 08:36 
Chuck Karish17 Dec 2004 21:38 
Subject:[p4] Unwanted new timestamps after submit
From:Robert Cowham (rob@vaccaperna.co.uk)
Date:12/08/2004 07:36:14 AM
List:com.perforce.perforce-user

Another alternative is to use a build system like scons (www.scons.org) which defaults to using MD5 digests of contents to detect file changes rather than timestamps...

It seems to me that every company using Perforce in connection with big C++ projects and RCS keywords would run into this problem. This makes me hope that somebody can recommend a solution :-)

Basically, what I am looking for is an option to update the file timestamp after a sync operation, but to not update it after a submit.

Thanks in advance, Max.