[p4] substantial reorganisation - Russell C. Jackson - com.perforce.perforce-user

5 messages in com.perforce.perforce-user[p4] substantial reorganisation

From	Sent On	Attachments
Jason Trenouth	30 Apr 2001 14:53
Russell C. Jackson	02 May 2001 11:50
Chuck Karish	02 May 2001 13:07
Stephen Vance	02 May 2001 13:37
Jason Trenouth	02 May 2001 14:16

Subject:	[p4] substantial reorganisation
From:	Russell C. Jackson (rcja...@comcastnet.com)
Date:	05/02/2001 11:50:56 AM
List:	com.perforce.perforce-user

It doesn't double up the info. in the server because Perforce doesn't actually copy the info. over when you do a branch until you start modifying it. It is what is called a lazy copy, so unless you just don't want the old directory structure to show up when show deleted files, there is no reason to start over.

Rusty

-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Jason Trenouth Sent: Monday, April 30, 2001 2:54 PM To: perforce-user at perforce.com Subject: [p4] substantial reorganisation

Hi,

We're new users of Perforce. Our initial import of the sources of a pilot project into Perforce now requires a substantial reorganisation to cope with the evolution of the product and allow it to cohabit a depot with other projects.

I know the standard technique is to integrate and delete. However, some of the developers are concerned that this will effectively double up a lot of information on the server. They would like to archive the current setup given that its only captured a month or two of development and start again. I'm concerned that if we don't get into good habits now then we never will.

Any comments on the strategies given that I haven't provided any concrete numbers...?

__Jason