[p4] Difference in integration behavior in 2006.2

[Stephen Vance]

Hi, Bill --

Selective integration of only revision 8 may implicitly integrate the 
*contents* of revision 7, but does not integrate the revision 
explicitly. The integration accounting should recognize that only 
revision 8 was integrated.

I would attribute the change in behavior to the new integration 
algorithms. I believe they were motivated by these kinds of situations 
in which the integration accounting wasn't quite precise.

It wouldn't hurt to report it as a bug. They can reject it if it's by 
design. I don't think anyone outside of Perforce could realistically do 
more than make educated guesses at it. They'll probably also want a 
checkpoint so they can dig into the details.

Steve

Leonard, William C wrote:
> I don't know for sure, but I expect it was done as a selective
> integration.  That's the usual practice.
>
> However, since the integration was resolved as a "copy from", it DOES
> include revision 7, since revision 8 includes the contents of revision 7
> (which includes the contents of revision 6, etc.).  I realize that the
> programmer may not have explicitly SAID to include revision 7 in the
> integration, but he implicitly did so when he resolved it by accepting
> the source.  This is true regardless of whether revision 7 made any
> actual changes to the file.
>
> Our main question was why we started seeing this change in behavior, and
> whether it's a bug or a feature?  If it was intentionally changed to be
> this way, then I wouldn't want to report it as a bug.
>
> William Leonard
> Executive Manager
> Security, Government & Infrastructure (SG&I) Division
> Intergraph Corporation
> P.O. Box 6695, Huntsville, AL 35824-0695 USA 
> P 1.256.730.8167   F 1.256.730.1717
> bill.leonard at intergraph.com, www.intergraph.com
>