[p4] Explain this interchanges dilema?

George Muresan gmuresan at workforcesoftware.com
Mon Aug 16 12:51:17 PDT 2010

Does anyone have an update on this issue? Was this solved, or is there a workaround?

George Muresan | Software Engineer | WorkForce Software | P: (734) 542-4100 x285 | gmuresan at workforcesoftware.com
WorkForce Software - Mitigating Complexity - Ensuring Compliance - Enabling Strategic HR
Don't forget to register for Vision 2010, WorkForce Software's user conference in Orlando, FL from November 7-10, 2010.  Register now!

--Original Message--

Roy --

We've encountered a couple of false positives in interchanges a while ago. Briefly, our issue was that if one (later) change was cherry-picked and
integrated, while another (earlier) change was not, interchanges would keep
reporting the later change as needed to be integrated. If you run "p4 integ" against that change, it would correctly say that all
revisions were integrated. Your case sounds very much like this one.

We opened a support call (#987040) with Perforce some time ago, but we believe
they don't have plans to fix this soon.

More information about the perforce-user mailing list