[p4] Change numbers not in chronological order?

Robert Cowham robert at vizim.com
Tue Mar 3 17:11:19 PST 2009


It's not terribly tricky - as a superuser you can use "p4 change -f 10446"
and update fields including the date/time of submit.

Ordinary mortals can only update the description of a submitted changelist
(with recent servers and if they submitted it).

As to when this feature is used - it is pretty common for all of the
import/migration scripts to do it.

It does break the relationship between increasing changelist no and
increasing date/time which can be a surprise, but in this sort of case it's
usually worth it. A key guideline is to only do it for a specific part of
your depot, which could be //import or similar.

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Grills, Jeff N
> Sent: 03 March 2009 19:12
> To: Roy Smith; perforce-user at perforce.com
> Subject: Re: [p4] Change numbers not in chronological order?
> 
> Those files out of order came from cvs2p4.  Perhaps that tool 
> attempts to preserve the original submission date through 
> some trickery?
> 
> j 
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Roy Smith
> Sent: Tuesday, March 03, 2009 12:55 PM
> To: perforce-user at perforce.com
> Subject: [p4] Change numbers not in chronological order?
> 
> I just did "p4 changes ..." on a portion of our source tree.  
> The very end of the output looked like this:
> 
> Change 10446 on 1993/04/09 by ouster at cvs2p4 '.  [imported 
> from CVS by cvs2p4'
> Change 10437 on 1993/04/03 by ouster at cvs2p4 'Branching  
> [imported from CVS b'
> Change 10435 on 1993/04/01 by ouster at cvs2p4 'Branching  
> [imported from CVS b'
> Change 10433 on 1993/03/19 by ouster at cvs2p4 'Branching  
> [imported from CVS b'
> Change 10432 on 1993/03/19 by ouster at cvs2p4 '.  [imported 
> from CVS by cvs2p4'
> Change 10426 on 1993/02/06 by ouster at cvs2p4 '.  [imported 
> from CVS by cvs2p4'
> Change 10425 on 1991/09/08 by ouster at cvs2p4 'Branching  
> [imported from CVS b'
> Change 10410 on 2006/12/15 by helenw at USENHELENWD2E 'code refactory '
> Change 10391 on 2006/12/14 by pogren at pogren_ECOM 'Start work 
> converting stream op'
> Change 10388 on 2006/12/14 by buncew at build-san-mediation-all 
> 'remove disconnect of s: drive '
> Change 10387 on 2006/12/14 by buncew at build-cimom-all 'remove 
> disconnect of s: drive a'
> Change 10383 on 2006/12/14 by gaih at gaih-ecom-andvm5 'Modified 
> MOF to have start, sto'
> Change 10381 on 2006/12/14 by steng at p4webapps 'modify for 
> build environ '
> 
> How it is possible that the changes are not in chronological 
> order?  I thought it was a fundamental P4 constraint that 
> increasing change numbers always represent increasing time.



More information about the perforce-user mailing list