[p4] Fixing a Branch to Reflect an Earlier Release

[Melissa]

You are in the right track with trying to integrate the revision that you
want... But you have to force integrate.

Beware of files that exist in the latest revision, but not in the earlier
revision. You will have to delete them by hand.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Vander Werf, Bruce
Sent: Wednesday, February 21, 2007 8:27 AM
To: perforce-user at perforce.com
Subject: [p4] Fixing a Branch to Reflect an Earlier Release


We have a situation here where a release branch was created based on the
latest revision in the main codeline, but it should have been created on an
earlier revision. How can I repair this so that the release branch reflects
the correct revision? 
 
I tried integrating that revision from the main branch to the release
branch, but it reported that the revision had already been integrated. 
 
Can I use obliterate to just destroy the branched revision and re-integrate?
 
-Bruce
 
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user