[p4] Fixing a release branch

[Ivey, William]

> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of Vander Werf,
> Bruce
> 
> We branched our main codeline as a release branch, only to 
> realize that
> we had included changes made since the point of release. I 
> would like to
> do this again at an earlier point (changelist), but I'm not sure the
> best way to do this.
>  
> I can obliterate the bad branch, but I am worried about side effects.
> When I tested this, the report was 'Would delete 594 client 594
> integration 297 revision records.' There have been no revisions to
> the branch, so I'm concerned about what this actually deleting.

That's normal. When you obliterate files you also obliterate the records associated with them. (If I interpret the numbers correctly,
it's 297 files, with a source and destination record for each in
the client and integration tables, or something like that.)

After obliterating, you do need to make sure anyone who synced the
files removes them from their workspace. Perforce won't do it
since it has no record of them anymore.

-Wm