[p4] Mapping files in Depot to actual Perforce Storage
steve at vance.com
Thu Oct 12 16:34:29 PDT 2006
1) While it's theoretically possible, it never happens.
2) Binaries are compressed unless they have the +F file modifier. It is
common practice to add the +F modifier for file types that are already
compressed such as zip, gif, jpeg, mpeg, etc.
3) Yes. Files are only copied once edited after a branch operation.
4) Yes, that is correct.
Weintraub, David wrote:
> I have decided to implement a script like Richard Baum's trigger which
> removes obsolete binary versions of a file. I have a few minor
> 1). I notice that the binary files names are usually 1.X.gz where "X" is
> the revision number of the file. Why do they start with "1."? Could a
> file be "2.X.gz"?
> 2). Are all binaries "compressed, so I will expect revision #5 of a file
> to be "1.5.gz" and never "1.5"? Or, do I need to look at the file type
> and somehow determine whether or not it is compressed.
> 3). I notice that "1.1.gz" is missing in some files. Is this due to the
> "lazy copy" from a branch?
> 4). I want the ability to verify that a particular version of a file
> contains no labels. Is the best way to do a "p4 labels
> <fileName>#<version>" and see if any labels are listed?
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user