20 messages in com.perforce.perforce-user[p4] renaming files in perforce is ok
FromSent OnAttachments
Peter E Hecht12 Jun 2001 08:46 
Ines Heinz12 Jun 2001 09:36 
Christian Goetze12 Jun 2001 09:42 
Arnt Gulbrandsen12 Jun 2001 10:25 
Chuck Karish12 Jun 2001 10:25 
Richard Geiger12 Jun 2001 10:34 
Jeff A. Bowles12 Jun 2001 10:56 
tr...@treysoft.com12 Jun 2001 11:08 
Chuck Karish12 Jun 2001 11:28 
Christian Goetze12 Jun 2001 11:42 
Dave Foglesong12 Jun 2001 11:53 
Chuck Karish13 Jun 2001 10:33 
Jeremy Russell13 Jun 2001 10:51 
Christian Goetze13 Jun 2001 11:27 
Dave Lewis13 Jun 2001 11:45 
Doug Quist13 Jun 2001 12:41 
Stephen Vance13 Jun 2001 14:26 
Chuck Karish13 Jun 2001 14:34 
Craig Allsop13 Jun 2001 15:37 
Richard Brooksby14 Jun 2001 07:02 
Subject:[p4] renaming files in perforce is ok
From:Christian Goetze (cg@digisle.net)
Date:06/13/2001 11:27:49 AM
List:com.perforce.perforce-user

On Wed, 13 Jun 2001, Chuck Karish wrote:

At 04:42 PM 6/12/2001 +0000, Christian Goetze wrote:

2) When you rename a file but don't submit, and meanwhile somebody else submits a content change to the now deleted file, you won't see those changes in the new file - or will you? This is what makes source tree re-orgs a big deal, because everybody has to stop working while you do it.

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?

The point is that I have to coordinate with everybody, I can't just go out and reshape the world :)

-- cg