-----Original Message----- From: Jones, Bruce [mailto:brjones at enterasys.com] Sent: Montag, 19. November 2001 19:35 To: 'Kimberly McClintock'; Perforce-User (E-mail) Subject: RE: [p4] Branching...

Some people are against checkpoint surgery, but I have used it successfully several times.

<Use at your own risk disclaimers here> We have used this method to move things around in the depot because of the same situation you mention. The way we did it is like this:

Take a checkpoint.

Create a sed script that replaces every instance of //depot/<filename> with //depot/<new subdir>/<filename>

Run sed on the checkpoint.

Create the directory /depot/<new subdir> in the Perforce root area

Move the all affected files from /depot to /depot/<new subdir>

Restore from the sed altered checkpoint.

The reason I like this is because this changes all references to the file, in changlists, branch specs, labels, whatever. Wherever there is a reference to the old location it gets changed to the new location, invisibly. It looks like things have always been in the new location. The only area that may be a problem is Makefiles or such that use the old paths.

Note we tested this on copies of the depot and checkpoints before doing it for real.

2nd Note, we did this before Perforce had the option to follow file history across branches. That may make integration a better option now. I still like surgery in some situations though.

Bruce