[p4] Re: Labels or branches?
Simon.Morton at MetraTech.com
Fri Jun 8 07:26:19 PDT 2001
This is certainly a bit confusing until you realize what is going on.
I was using a change daemon which was polling `p4 counter change` to
figure out when something had changed. It took me a while to realize
that the change counter didn't always change when a change list was
submitted. For example:
Action `p4 counter change`
user 1 submits change 50 50
user 2 creates pending change list 51 51
user 3 creates pending change list 52 52
user 2 submits change list 51 52
user 3 submits change list 52 52
If you are polling on `p4 counter change` to detect when a change list
is submitted, you will miss both 51 and 52.
You need to use `p4 changes -s submitted -m 1` and parse out the change
number to find the last change list submitted.
> -----Original Message-----
> From: Tadd Ottman [mailto:tadd at docent.com]
> Sent: Thursday, June 07, 2001 8:35 PM
> To: Gordon Broom; perforce-user at perforce.com
> Subject: RE: [p4] Re: Labels or branches?
> Your reply and others have forced me to rethink my experience, for I
> was burned by such a discrepancy recently when reconstructing an old
> build. Now I have concluded that the old build was identified by
> a 'p4 counter change' value rather than the latest submitted
> value. In this situation, the value might have been associated with
> a pending changelist that was submitted without a need for
> It is comforting to me to learn about the renumbering practice, but
> the case reinforces the importance of using the latest *submitted*
> changelist value to identify a build rather than using the current
> value of the change counter.
> > -----Original Message-----
> > From: Gordon Broom [mailto:Gordon_Broom at pml.com]
> > Sent: Thursday, June 07, 2001 5:05 PM
> > To: 'Tadd Ottman'; perforce-user at perforce.com
> > Subject: RE: [p4] Re: Labels or branches?
> > Thus spake Tadd Ottman:
> > >To clarify, this is *not* a problem with pending <default>
> > >since they are assigned new changelist numbers greater
> than that which
> > >identifies your build. The problem is submittals of
> changelists created
> > >with "p4 change" or the <Update> button in P4Win before
> your build and
> > >submitted after your build. When reconstructing your build in the
> > >future, your "p4 sync" will incorporate such changes even
> though your
> > >original build did not.
> > Changelists created with 'p4 change' get renumbered when
> submitted, if
> > another change has occurred in the meantime. P4 will inform
> > you when this
> > occurs.
> > Gord Broom
> > Configuration Management Engineer
> > Power Measurement Ltd.
> > http://www.pml.com/
> > +1 250 652 7100 x7608
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user