Re: Confusing change number info in smoke status

Abe Timmerman wrote:

> and right after your p4 update, you should write that number to F<.patch> in 
> your "master-tree", that should solve this inconsistency.
:
> Yup, *I* fake F<.patch> in Test::Smoke::Syncer for the case none was found, 
> and found (at least in Jarkko's snapshots) that the change that commits the 
> MAINTxxxxx is xxxxx+1, so I bump it one (Test/Smoke/Syncer.pm:311).
> I use this for the case where smokers use the snapshots as the base for a 
> clean sourcetree and apply all individual patches after that changenumber 
> (from the right branch). Some people have problems rsync()ing from behind a 
> firewall and most of them do not have access to p4.

That explains it then, it is Smoke that is creating the .patch files. 
As suggested, I'll modify my master script to create a .patch file in 
the p4 sync'd clone with the correct number in it, then it should all 
work OK.

> (one often wonders "how random is rand() when it's picking these sigs")

Are you sure that was one of mine?  It looks far too witty and erudite ;-)

-- 
Alan Burlison
--