Re: Confusing change number info in smoke status

Nicholas Clark wrote:

> I suspect that your p4 changes command is getting the latest change anywhere
> in the repository. Compare:
> 
> $ p4 changes -m1
> Change 22084 on 2004/01/07 by rgs@sixop 'Hardcoded numerical flag masks.'
> 
> $ p4 changes -m1 //depot/maint-5.8/perl/...
> Change 22081 on 2004/01/06 by nicholas@entropy 'Move pod/perldelta.pod to pod/p'
> 
> You'll want the latter.

Nope, al already use the apprpriate //depot goop to get the change for 
each branch:

Repository branch for perl 5.6.x
   Latest change number is 21880
Repository branch for perl 5.8.x
   Latest change number is 22081
Repository branch for perl 5.9.x
   Latest change number is 22083

> As to why the patch number and the local_patches level differ like that,
> I'm not sure.
> The line MAINT21995 only gets updated when the Changes file is updated
> (which is done by a script that Jarkko gave me, but I have to fire that by
> hand). So it can be quite out of date. (Which reminds me that this is
> not obvious, and when Randal uses that value to report things it's not
> actually that useful)
> 
> However, I'm confused as MAINT21995 was added as change 21998 (not 21996)
> If you'd said 21998 then I'd expect that the explanation was that you'd
> happened to sync just after the change. Either that or you're faking the
> .patch number, because that file is added by the system that makes the
> rsync master, not p4.

I have no idea where the .patch file is coming from, as it certainly 
doesn't appear in my p4 sync'd clone, but it does appear in the master 
rsync archives that Smoke builds (I'm using the Smoke rsync support).

-- 
Alan Burlison
--