[p4] Changelist-at-a-time VS bulk integration

[Ed Mack]

Our CM team used to do the mass merges, but now we integrate by
changelist almost exclusively.  We have a script that calls the
(undocumented) "interchanges" command to spit out the unintegrated
changes (using a list of branchspecs).  The script parses the output and
formats email notifications to the changelist owners of their list of
changelists that need integrating.

This works very well for us.

Ed

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Rick 
> Macdonald
> Sent: Friday, December 08, 2006 12:25 PM
> To: Perforce Users Mailing List
> Subject: [p4] Changelist-at-a-time VS bulk integration
> 
> The current thread about Cherry-picking reminds me that I 
> never heard or 
> thought about integrating one changelist at a time. I just do 
> everything 
> at once and hope for the best. Mostly it's fine. Things can get 
> complicated, but it's always been doable.
> 
> I first came across the one-at-a-time idea in Laura's book. I 
> won't give 
> an example; I'll assume folks here know what I'm referring to.
> 
> Any comments about this? Does anybody do it always? Just when 
> you think 
> you might need to? Never?
> 
> ...RickM...
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>