[p4] Integrate just one change

[Christopher Chong]

I agree.  When I first started using Perforce I did some integrations by
changelist only b/c I thought it would work like Clearcase and bring all the
previous changes along for the ride.  Nope.  As Stephen said, it only takes
the deltas of that version.  So if the user changed foo.c#2 in change 1000
and foo.c#3 in change 1001, then integrated @1001, at 1001, you'll only get the
deltas between 1000 and 1001.  In Clearcase, if you integrated the head
version, it would automatically take all the changes from the "root"
version.

We use developer branches and integrate on approval instead...

--Chris

> -----Original Message-----
> From: Stephen Vance [mailto:steve at vance.com]
> Sent: Tuesday, July 31, 2001 6:05 AM
> To: david.hildebrandt at redspark.com; perforce-user at perforce.com
> Subject: Re: [p4] Integrate just one change
> 
> 
> At 05:25 PM 7/17/2001 -0700, david.hildebrandt at redspark.com wrote:
> >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.
> 
> Integrating a single change list can be a very effective 
> technique for 
> selectively composing a release, promotion, one-off build, 
> etc.  Realize 
> however that its very nature is to take only the deltas 
> supplied by one 
> version and apply them to a context different from that of 
> the original 
> fix.  Using this as your primary means of integrating 
> developers fixes may 
> cause you some problems.  You would be better off assigning a 
> branch to 
> each developer or each project and integrating changes down 
> to main as they 
> are completed and approved, then integrating everything up to 
> release when 
> you are ready to compose a release.
> 
> 
> Stephen Vance
> mailto:steve at vance.com
> http://www.vance.com/
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>