[p4] Changes since last label

Mike Castle mcastle at yy.com
Tue Apr 24 15:37:14 PDT 2001


On Tue, Apr 24, 2001 at 02:46:09PM -0700, Jeff A. Bowles wrote:
> Now, using a (pathname, changenumber) combination is sufficient to
> represent a release. Always. (I disagree with Diane on this part.)  But

Not always.

>          handoff #1:     build out of the normal development codeline,
>                          identified as "//depot/devline/... at 12367".

Let's say you also are required to archive the results of the build
process.  You either have to branch immediately, and protect that branch,
or you have to use labels.  Otherwise you have a race condition:

p4 sync
p4 edit build.results
build
                      Another developer makes a change
p4 submit build.results
echo "You just built `p4 where ... | awk '{print $1}'` at `p4 counter change`"

Of course, that isn't sufficient, because the changes the other developer
made are not part of this build.

mrc



More information about the perforce-user mailing list