[p4] How to make a change I know I'll have to back out later? - Chuck Karish - com.perforce.perforce-user

5 messages in com.perforce.perforce-user[p4] How to make a change I know I'll...

From	Sent On	Attachments
Kaelin Colclasure	11 Oct 2000 18:18
Amaury FORGEOT-d'ARC	12 Oct 2000 01:51
Mike Morris	12 Oct 2000 05:11
Chuck Karish	12 Oct 2000 06:57
Gil Tayar	12 Oct 2000 09:20

Subject:	[p4] How to make a change I know I'll have to back out later?
From:	Chuck Karish (kar...@bea.com)
Date:	10/12/2000 06:57:32 AM
List:	com.perforce.perforce-user

At 05:11 AM 10/12/00, Mike Morris wrote:

This is an excellent candidate for a branch. I would branch the sources and make the temporary change in the branch. The "real" change can then be made on the main line. This permits the change to be archived in the Perforce repository at the same time it does not clutter your main code with quick-fix junk.

I agree completely. I'd branch the whole code line into my sandbox. I'd occasionally do an integration from the main line to my branch, so I wouldn't have an integration nightmare when it was time to move the changes back to the main line.

The cost to be paid is in the size of the db.have file. Big, fast disks. Say it to yourself. Say it to your manager. Less expensive by far than one project that gets delayed a week because developers don't have a proper place to work.