[p4] Query about integ - Stephen Vance - com.perforce.perforce-user

5 messages in com.perforce.perforce-user[p4] Query about integ

From	Sent On	Attachments
Biju George	10 May 2004 01:24
Oren Shemesh	10 May 2004 02:02
Stephen Vance	10 May 2004 05:46
Biju George	10 May 2004 06:08
Oren Shemesh	10 May 2004 06:55

Subject:	[p4] Query about integ
From:	Stephen Vance (ste...@vance.com)
Date:	05/10/2004 05:46:23 AM
List:	com.perforce.perforce-user

I agree that this is likely the case. By default when labelling, deleted revisions are not included in the label and would therefore not count as part of the source for the integ. Deleted revisions can be added to the label explicitly by revision. Alternatively, use a specific revisions specifier (e.g. @237, #head) when initially creating the label, rather than creating from the workspace contents.

Steve

At 05:03 AM 5/10/2004, Oren Shemesh wrote:

Using a branchspec has nothing to do with it. The problem might be that the label you are using for the 2nd integ does not contain the deleted file, hence it is not included in the 'integ' operation.

Oren.

-----Original Message----- From: Biju George [mailto:bgeorge at sasken.com] Sent: Mon, May 10, 2004 11:24 AM To: perforce-user at perforce.com Subject: [p4] Query about integ

Hi,

I've come across a situation where an 'integ' operation does not mark 'deleted source files' for delete in the target path.

To elaborate, the original integ was carried out without a branchspec. Subsequently, some files have been deleted in the source path. Now, when I try to 'integ' files (this time using a labelspec ), the deleted source files are not opened for deletion in the target path.

Is this how it is supposed to behave? Is there a way I can force to mark target files for deletion? Do I necessarily need to use a branchspec for the target files to be marked for 'delete'?

PS: I tried the -d option along with -i, but it does not work.