[p4] renaming files in perforce is ok - Chuck Karish - com.perforce.perforce-user

20 messages in com.perforce.perforce-user[p4] renaming files in perforce is ok

From	Sent On	Attachments
Peter E Hecht	12 Jun 2001 08:46
Ines Heinz	12 Jun 2001 09:36
Christian Goetze	12 Jun 2001 09:42
Arnt Gulbrandsen	12 Jun 2001 10:25
Chuck Karish	12 Jun 2001 10:25
Richard Geiger	12 Jun 2001 10:34
Jeff A. Bowles	12 Jun 2001 10:56
tr...@treysoft.com	12 Jun 2001 11:08
Chuck Karish	12 Jun 2001 11:28
Christian Goetze	12 Jun 2001 11:42
Dave Foglesong	12 Jun 2001 11:53
Chuck Karish	13 Jun 2001 10:33
Jeremy Russell	13 Jun 2001 10:51
Christian Goetze	13 Jun 2001 11:27
Dave Lewis	13 Jun 2001 11:45
Doug Quist	13 Jun 2001 12:41
Stephen Vance	13 Jun 2001 14:26
Chuck Karish	13 Jun 2001 14:34
Craig Allsop	13 Jun 2001 15:37
Richard Brooksby	14 Jun 2001 07:02

Subject:	[p4] renaming files in perforce is ok
From:	Chuck Karish (kar...@well.com)
Date:	06/13/2001 02:34:00 PM
List:	com.perforce.perforce-user

At 06:28 PM 6/13/2001 +0000, Christian Goetze wrote:

On Wed, 13 Jun 2001, Chuck Karish wrote:

Whoever submits the rename should lock the files under their old names and check whether integrations are needed before proceeding. This is problematic only if changes are integrated that require build and test before submitting.

But what happens if somebody was already working on that file before I started relocating/renaming it?

When that change is checked in I think the user gets a warning message that the renamed (deleted) file won't be restored without the '-d' flag. At that point the user merges the changes into the renamed file.