[p4] User initiated Codeline Freezes

Chuck Karish chuck.karish at gmail.com
Mon Aug 27 08:11:48 PDT 2007

On 8/27/07, todd.benham at kodak.com <todd.benham at kodak.com> wrote:
> Being relatively new to the 'Perforce way', if you don't freeze a branch
> (in whatever means), how do know what files where part of a particular
> version. Is there an assumption that it is labeled?  A general CM practice
> is to occasional rebuild (audit) older versions to prove the process
> really captured it correctly. If it is not frozen, how do you ensure it
> wasn't accidentally changed later (added to).

A changelist number defines a moment in the history of the code
line that can be used the same way you would use a label.  It
completely specifies the contents of the code line.

Syncing to the same changelist number always brings the same
bits into the client workspace.  Whether your build system does
the same thing with them is still worth auditing, but it's a separate

Chuck Karish   karish at well.com   (415) 317-0182

More information about the perforce-user mailing list