[p4] Integrate just one change

Russell C. Jackson rcjackson at alum.atu.edu
Mon Jul 30 21:24:40 PDT 2001


That is the correct approach, and as far as I know, the only way to move
just one changelist.

Rusty

Russell C. Jackson
rcjackson at alum.atu.edu

-----Original Message-----
From: perforce-user-admin at perforce.com
[mailto:perforce-user-admin at perforce.com]On Behalf Of
david.hildebrandt at redspark.com
Sent: Tuesday, July 17, 2001 5:26 PM
To: perforce-user at perforce.com
Subject: [p4] Integrate just one change


Hi all,

I'm converting our development organization from VSS (boo, hiss) to Perforce
(hip, hip, hurrah).  I have a few years of ClearCase experience.

I'd like to develop a process whereby my engineers can integrate just one
Perforce changelist from the main codeline into a release branch.  It seems
that I can specify the changelist number as the first and last version of an
integration of the entire main codeline to the entire release codeline.  If
I Preview this integration with P4Win, Perforce suggests the correct (i.e.
expected) list of files.

Does this sound like a decent approach?  We're going to use this process a
lot.

-d
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user





More information about the perforce-user mailing list