[p4] How to make a change I know I'll have to back out later?
Gil.Tayar at webcollage.com
Thu Oct 12 09:20:42 PDT 2000
Actually, our development environment is built around the concept of
sandboxes and we have multiple scripts that deal with the forward and
reverse integrations there (forward for moving changes from mainline into
sandbox and reverse for the reverse direction). For example, the reverse
integration is an atomic operation that is mutexed.
I totally agree with Chuck. This system needs big hard disks. Actually, we
didn't really understand the reason for this, as an integration link is just
a record somewhere - it's not as if the file is copied from one place to
another! What does the db.have file store that makes it so big in such a
system of mainline and sandboxes?
From: Chuck Karish [mailto:karish at bea.com]
Sent: Thu, 12 October, 2000 15:58
To: mikem at perceptron.com; perforce-user at perforce.com
Subject: RE: [p4] How to make a change I know I'll have to back out later?
At 05:11 AM 10/12/00, Mike Morris wrote:
>This is an excellent candidate for a branch. I would branch the sources
>make the temporary change in the branch. The "real" change can then be
>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
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.
Chuck Karish BEA Systems
karish at bea.com San Francisco, CA
(415) 317-0182 (cell) (415) 402-7692
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user