[p4] p4 interchanges question

Wesley Hunt weshunt at fusemail.com
Mon Oct 8 17:05:47 PDT 2007


p4 interchanges seems to report all revisions after the 1st
non-integrated revision as needing to be integrated, regardless of
whether those revisions have been integrated. Does anyone know if this
is intended or a bug?

It only matters when one "cherry-picks" a change for integration. For example:

<ASCII ART>

BranchRelease: Foo.txt - #1 ----- #2 ----- #3
                          ^                 |
                 (branch) |                 | (merge)
                          |                 v
BranchMain   : Foo.txt - #1----------------#2

[Let's please ignore the philosophical questions of whether this is a
good idea (yes, I've read Practical Perforce, etc... :). That ship has
unfortunately sailed]

    p4 interchanges -b ReleaseToMain

will report change #2 AND #3 need to be integrated. Obviously running

    p4 integrate -b ReleaseToMain //...Foo.txt#3,#3

will report

    all revisions already integrated.

So it seems p4 interchanges is not handling cherry-picking...?

-Wes


More information about the perforce-user mailing list