[p4] p4 integrate with p4 obliterate

Mon Oct 16 17:07:44 PDT 2000

Hello,

I needed to move some files around in my depot.  So,
using the p4 integrate/filespec command I
branched/moved my files to the needed directory.  (I
really just wanted a rename but that doesn't exist. 
And if you type p4 rename you are instructed to do a
p4 integrate then a p4 delete of the original file. So
I did.)

After integrating the files then submitting them,
there they were in the new directory and all the
revision history was there.  However, if I p4
obliterate the original file I lose the comment from
before the p4 integrate.

Is this a bug or expected behavior?

Best,
Sheryl

__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf!  It's FREE.
http://im.yahoo.com/

Message-Id: <4.3.2.7.2.20001016113950.00d66b40 at ashbury.beasys.com>
Date: Mon, 16 Oct 2000 11:54:57 -0700
To: andrew.r.bredhauer at transport.qld.gov.au, perforce-user at perforce.com
From: chuck.karish at bea.com (Chuck Karish)
Subject: Re: [p4] Label Owners and access permissions
In-Reply-To: <4A25697A.00134D74.00 at shb1ln11.transport.qld.gov.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: perforce-user-admin at perforce.com
Errors-To: perforce-user-admin at perforce.com
Precedence: bulk

Andrew,

You're trying to add workflow capabilities to p4 in a somewhat
unnatural way.

The natural way to do this would be to set up a sequence of branches
and integrate files from one stage to the next only when they meet
the release criteria to go to the next stage.

The common wisdom is that it's best to keep a through-going main
line (dev) and make a new set of branches when you do a release.

                     release 1
       /-- (prep1) ----+-- prod1 ->   /-------------- prep2 ------>
      /                              /
     /-------------------- syst1 -> /---------------- syst2 ------>
    /                              /
---------------------------------+-------------------------------> dev

When the "prep" line is ready to release it becomes "prod" and you
make new "syst" and "prep" branches.  The branches for the released
product would remain active in case patches were needed to support
the release.

At 08:31 PM 10/15/00, andrew.r.bredhauer at transport.qld.gov.au wrote:

>I'm using labels within Perforce to specify the environment that each file 
>is in
>i.e. development (dev), System Testing (syst). Pre-Production (prep) or
>Production (prod). First off I guess one question is is anyone else using 
>labels
>to do this or is there a better way?
>
>Next off the problem I'm having is that it seems only the label creator/owner
>can modify the list of files in that particular label. I would rather that the
>developer can move files into each environment (particularly the dev
>environment) as they are released. Is there a way I can set group 
>permissions on
>labels or somehow get Perforce to behave like this.
>
>The third question I have is is there a way that I can force that files must
>progress through the four labels in the correct order i.e. dev -> syst -> prep
>-> prod and not straight to prod or similar?
>
>Any ideas you have would be appreciated.
>
>Thanks
>
>Andrew Bredhauer
>
>---------------------------------------------------
>Computer Systems Officer
>Queensland Transport
>Email: andrew.r.bredhauer at transport.qld.gov.au
>Phone: (07) 3834 2265
>Fax:   (07) 3834 2911
>477 Boundary Street
>Spring Hill
>Queensland  4000
>Australia
>
>
>
>
>*************************************************************
>Opinions contained in this e-mail do not necessarily reflect
>the opinions of the Queensland Department of Main Roads,
>Queensland Transport or National Transport Secretariat, or
>endorsed organisations utilising the same infrastructure.
>If you have received this electronic mail message in error,
>please immediately notify the sender and delete the message
>from your computer.
>_______________________________________________
>perforce-user mailing list  -  perforce-user at perforce.com
>http://maillist.perforce.com/mailman/listinfo/perforce-user

        Chuck Karish                    BEA Systems
        (415) 402-7692                  http://www.bea.com/