[p4] Finding unintegrated changes

Jeff A. Bowles jab at pobox.com
Tue Nov 4 07:49:13 PST 2008

See Robert's comments.
Also, I believe that the output of "p4 changes -i" against each code tree,
would be instructive.  If you 'diff' that output (in the various
combinations) you will see what is included or not included in the codeline,
according to the integration records. This will give you
changelist-granularity, which is good ("useful and easy to understand") and
bad ("misleading, in that a partial changelist could be included and it
would look like it was completely included, so you have to check for that

   -Jeff Bowles

On Tue, Nov 4, 2008 at 5:17 AM, Yamuna Ramasubramaniyan <
YRamasubramaniyan at webroot.com> wrote:

> Hello,
> I have a project which has 4 branches, Main, R1, R2 and R3.  My task is
> to find changes in R1 that aren't in other branches.  I'm using the
> interchanges command but it doesn't help in the below case:
> *       Cl  #1 is submitted to main and integrated to R1 ( cl #2) and R2
> ( cl #3).  I can't figure out a way to determine that cl #2 was
> submitted to R2 and not R3.
> Our dev process is that changes are submitted to Main and integrated to
> R1, R2 etc.   In light of this confusion, I'm tempted to abandon this
> method.  What submission policy do you follow if there are multiple
> parallel development branches for a project?
> Thanks,
> Yamuna
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

Jeff Bowles - jeff.a.bowles at gmail.com

More information about the perforce-user mailing list