[p4] Problem with integrates

[Dave Lewis]

I have seen something like this in the past, and I was not able to pin
it down.  I think its a bug.

dave


On 7/18/07, Matt Roberts <mroberts at danger.com> wrote:
> > -----Original Message-----
> > From: Stephen Vance [mailto:steve at vance.com]
> > Sent: Wednesday, July 18, 2007 2:14 PM
> > To: Matt Roberts
> > Cc: perforce-user at perforce.com
> > Subject: Re: [p4] Problem with integrates
> >
> > Matt --
> >
> > At first glance this looks strange. I'd be interested in
> > knowing how the
> > workspace in which you are doing the integration is mapped. I would
> > suspect that this might have to do with that, but the fact
> > that you can
> > get it to work sometimes and not others would argue against that.
> >
>
> The workspace is pretty striaght forward, it contains in the view:
> //branches/old/...
> //branches/new/...
>
> No exceptions or anything weird.
>
>
> > Also try
> >
> > p4 integ -b branchspec -s @12345, at 12345
> >
> > The -s flag specifically says that the revision is the source
> > instead of
> > the "path from the target, revision from the source" interpretation
> > without it.
> >
>
> Tried, with the same result.
>
>
> > Also, is there a possibility that your "changing the names to protect
> > the innocent" obscures the communication of the problem? Or is your
> > translation of the details trivial?
> >
>
> I would think the translation would be trivial.  The only real
> difference b/t my example and the real thing is that the file is a
> little deeper in the tree than my example.  But I wouldn't call it
> extremely deep - 6 directories.  There are no odd-ball characters in any
> paths, no spaces, etc.
>
> Thanks,
> Matt
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>