[p4] Perforce dropping important stuff

Jeff A. Bowles jab at piccoloeng.com
Tue Jul 10 10:33:58 PDT 2001


At 08:18 AM 7/10/2001 -0600, Kimberly McClintock wrote:
>I have a situation: Our engineers have seen the following:
>Perforce dropping files from a changelist; Perforce dropping changes from 
>a file on merge.
>
>Wonder if anyone's seen the likes of this before? If there is a "known 
>bug" list out there somewhere?

Get thee to Tech Support. These are questions that you want
quick answers to, from folks who might've heard of them [from
another customer] already.

Dropping files from a changelist doesn't sound familiar.  There is
a situation where you might have it drop modifications from a merge,
which is understandable with a bit more information and MIGHT be
what you're talking about:
    * You open a file in a way that "schedules a resolve". (In other words, 
you open it for edit and it's not the most current revision that you're 
editing and then you try to 'p4 submit', or you open for integrate. The 
term "schedules a resolve" translates to "writes some temporary things to 
the database saying that when you run 'p4 resolve' that it'll be pulling 
content from somewhere and identifies the YOURS/THEIRS/BASE revisions 
that'll drive the resolve.")
    * During the resolve, you select the "lazy copy" option - which is 
"accept theirs".
    * You erroneously assume that Perforce will take the local copy of the 
file when you submit, and check it in, so you make it writeable ("chmod" or 
setting the write attribute on the file) and add a few quiet hacks to the 
file.
    * You submit it, and then when you look, you see that your extra hacks 
from the previous step - made outside of 'p4 resolve' - aren't there. (By 
the nature of "accept theirs", they're not supposed to be. But it's tough 
to explain that to the person who hacked the file in the previous step.)
I can't say that you're running into this, because you didn't give a lot of 
background in your question.

Anyhow, follow this up to support at perforce.com....

         -Jeff Bowles
         Perforce Consulting Partner

ps. I don't know of a "known bug" list for the Perforce product. There is 
the "fixed bugs" list (along with new features) in the release notes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/20010710/e195775f/attachment.html>


More information about the perforce-user mailing list