27 messages in com.perforce.perforce-user[p4] Perforce vs VSS (again)
FromSent OnAttachments
Stephen Ng09 Apr 2002 06:50 
Jeff A. Bowles09 Apr 2002 08:18 
Chuck Karish09 Apr 2002 08:35 
Stephen Ng09 Apr 2002 08:48 
Stephen Ng09 Apr 2002 09:02 
Hemantharaju Subbanna x483209 Apr 2002 09:43 
wiv...@us.itmasters.com09 Apr 2002 10:00 
Jeff A. Bowles09 Apr 2002 10:02 
Mike Pagel09 Apr 2002 10:03 
Raju Subbanna X483209 Apr 2002 10:33 
Dan Kegel09 Apr 2002 10:39 
Mike Pagel09 Apr 2002 10:41 
Dave Lewis09 Apr 2002 11:50 
Dave Lewis09 Apr 2002 12:30 
Chuck Karish09 Apr 2002 21:59 
Chuck Karish09 Apr 2002 22:08 
Fredric10 Apr 2002 01:41 
Stephen Ng11 Apr 2002 06:50 
Ed Mack12 Apr 2002 23:18 
Todd Blanchard15 Apr 2002 16:35 
Stephen Ng15 Apr 2002 17:13 
Robert Cowham15 Apr 2002 23:14 
Chuck Karish16 Apr 2002 01:55 
Arnt Gulbrandsen16 Apr 2002 02:27 
Stephen Ng16 Apr 2002 03:57 
Chris Trueman16 Apr 2002 10:48 
Diane Holt16 Apr 2002 11:38 
Subject:[p4] Perforce vs VSS (again)
From:Raju Subbanna X4832 (hema@nsc.com)
Date:04/09/2002 10:33:57 AM
List:com.perforce.perforce-user

Mike Pagel wrote:

Good point, a branch is faster under P4. This is nice too, but one could argue that branching doesn't happen that often.

Have a doubt here!

How does lazy copy make sure of the existence of the files if the original files from which branch copy was made is deleted/obliterated. Havn't tested it myself. I am sure this is a special case, but heck..happens.

A regular p4 delete does not do anything to the lazy copy in the branch, it's just another (dead) revision on top. If the original file is obliterated, the lazy copy will become a physical one.

You can actually do this copy type conversion explicitly w/o obliterating files, with p4 obliterate -z.

Mike

------------ % p4 help obliterate

obliterate -- Remove files and their history from the depot

p4 obliterate [ -y -z ] file[revRange] ...

Obliterate removes files and their history from the server in a way that they won't come back. (See 'p4 delete' for the non- destructive way to delete a file.) It retrieves space used by those files in the archive and then clears the files from all lists maintained by the server. Files in client workspaces are not affected, except that Perforce will no longer recognize them : : :etc..

-----------

But with -z option it does otherwise??