3 messages in com.perforce.perforce-user[p4] Re: obliterates and branches (Da...
FromSent OnAttachments
Dennis Wheeler23 Feb 2000 12:39 
Paul Goffin24 Feb 2000 08:35 
Rick Macdonald24 Feb 2000 08:46 
Subject:[p4] Re: obliterates and branches (Dave Lewis)
From:Dennis Wheeler (denn@pictureiq.com)
Date:02/23/2000 12:39:35 PM
List:com.perforce.perforce-user

Message: 8 Date: Wed, 23 Feb 2000 11:16:38 -0600 (CST) From: Dave Lewis <dlewis at vignette.com> To: dlewis at vignette.com CC: chuck.karish at weblogic.com, perforce-user at perforce.com Subject: Re: [p4] obliterates and branches

> Date: Wed, 23 Feb 2000 10:52:58 -0600 (CST) > From: Dave Lewis <dlewis at vignette.com> > > > > At 02:46 PM 2/22/00 , Dave Lewis wrote: > > >If I have a branch, and I obliterate the code the branch > > >comes from, will I be removing the branch as well? > > > > > >dave > > > > I can't think of many uses for a branch that > > maps non-existent files to non-existent files. > > The scenario is that a user created some files in the wrong > place, and then used integrate to move them to the right > place...

I realize now that I haven't been clear! I just want to oblit the files that were put into the wrong place, and leave the versions that were integrated into the right place. I don't believe a branch spec was ever involved in the process.

thanks to all for the info, btw!

Dave,

Is this your scenario?

1) create/submit some files # albeit in the wrong location 2) integrate said files to correct location # we'll call it a branch 3) obliterate original files # bye-bye

Your question: Will the "newly branched" files be removed as well? Answer: No. And as a bonus, I believe your revision histories, from the now defunct files, are updated/transfered to the "new branch" as well (but I haven't tested the bonus part).

-- Dennis