[p4] Change numbers not in chronological order?

Roy Smith smith_roy at emc.com
Tue Mar 3 10:54:53 PST 2009


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.

-------------------
Roy Smith <smith_roy at emc.com>
Software Guy, EMC
1133 Westchester Ave, 3rd floor
White Plains, NY 10604
+1 914 461 3597
AIM: roysmith649




More information about the perforce-user mailing list