[p4] Has change propagated ?

Robert Cowham robert at vizim.com
Wed Mar 11 04:30:00 PDT 2009

Don't forget "p4 integ -n" to show you what integrations Perforce thinks
need to be done.


	p4 integ -n source/... at 1456 target/...

Tells you if any revisions up to and including changelist 1456 need to be

Other options include:

	p4 integ -n source/... at 1456, at 1456 target/... 

Which does the same for the range of 1456 to itself, i.e. only that
changelist, so all revisions in that changelist, whether 10,000 or 1.

If nothing needs to be integrated, then it has already been done (doesn't
say what the resolve was though - could have been an ignore or -ay).


> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of G Barthelemy
> Sent: 11 March 2009 11:08
> To: perforce-user at perforce.com
> Subject: [p4] Has change propagated ?
> I am trying to find out if a particular changelist has 
> propagated. By "propagated" I mean that for each file in the 
> changelist, I want to know if any revision (on the same 
> branch) since - and including the revision submitted with the 
> changelist - has been integrated to any other branch (I am 
> not interested in excluding backed out changes).
> Basically, I think that what I really want, is for "p4 
> integrated" to support changelists, revision ranges and 
> integrate actions as revision specifiers or output filters. 
> Or alternatively, for the opposite of the p4 interchanges command.
> But in the mean time, I believe this can only be achieved by 
> scripting. I was thinking along those lines:
> take a change
> p4 describe it
> for each depotFile#rev, run p4 integrated depotFile
>   for each integrate action (how) matching "into"
>     if endToRev >= rev then break and bingo, change has 
> propagated to fromFile (yes "fromFile" is the destination 
> when integration action is "into").
> Has anyone got a better idea ? To me it seems expensive 
> (think changelist with over 10000 file revisions, which would 
> result in running as many integrated commands).
> Cheers,
> Guillaume
> _______________________________________________
> 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