[p4] Deleting original depot without affecting branch
william_ivey at bmc.com
Tue Mar 4 13:37:01 PST 2008
You don't want to run p4 snap before using p4 obliterate, they
are unrelated commands.
P4 obliterate will correctly handle lazy copies in the most
efficient way. P4 snap, on the other hand, will cause all
lazy copies found in the given path to be replaced by real file
copies. This will eat up repository space; possibly a great
deal of space.
P4 snap is overkill in most cases. Only if you want to make
sure that the files are redundantly stored would you want to
use it. This is not something most people will want to do
for most files.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Gabor Maghera
Sent: Tuesday, March 04, 2008 2:07 PM
I am little bit confused about the necessity of running p4 snap when
p4 obliterate. The help on p4 obliterate for version 2007.2, does not
anything about having to run p4 snap prior to using p4 obliterate.
So, I wonder, in order to preserve revisions for which you have lazy
in other branches, do you have to first run p4 snap? Has there been a
change to the obliterate algorithm going from p4d 2007.2 to p4d 2007.3,
On Thu, Feb 28, 2008 at 7:33 AM, Oren Shemesh (oshemesh)
<oshemesh at cisco.com>
> Thanks Paul, indeed the latest 'p4 help obliterate' shows that quoting
> from memory is a bad habit (at least when it comes to MY memory).
> Read 'p4 help snap' and 'p4 help obliterate' - they explain
> very clearly.
> -----Original Message-----
> From: paul goffin [mailto:paul.goffin at dsl.pipex.com]
> Sent: Thursday, February 28, 2008 12:17 PM
> To: Oren Shemesh (oshemesh)
> Cc: Jeff Desharnais; perforce-user at perforce.com
> Subject: Re: [p4] Deleting original depot without affecting branch
> Not with recent versions of the server it doesn't.
> See "p4 help snap".
> Quoting "Oren Shemesh (oshemesh)" <oshemesh at cisco.com>:
> > Obliterate automatically does the work '-z' would do, if needed.
> > You can safely use obliterate, just as you understood in the past.
More information about the perforce-user