Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 users |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 where |
If invoked without arguments, p4 verify computes and displays the MD5 digest of each revision. If a revision is missing from the archive and therefore can't be reproduced, the revision's output line ends with MISSING! If the digests differ, the output line for the corrupt file ends with BAD!
-q |
Run quietly; verify the integrity of files for which MD5 digests have previously been generated, and only display output if there are errors. |
-u |
Store the filesize and MD5 digest of each file in the Perforce database if and only if no filesize and/or digest has been previously stored. Subsequent uses of p4 verify will compare the computed version against this stored version. |
-v |
Store the MD5 digest of each file in the Perforce database, even if there's already a digest stored for that file, overwriting the existing digest. (The -v flag is used only to update the saved digests of archive files which have been deliberately altered outside of Perforce control by a Perforce system administrator.) |
-m maxRevs |
Limit p4 verify to maxRevs revisions. |
See the Global Options section. |
Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 users |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 where |