[p4] p4 verify question

[Matt Janulewicz]

Hello -

I have inherited a nightly/weekly maintenance script that runs a verify 
on a large set of data over the weekend. This sometimes takes more than 
12 hours (per day! It's split in half!) Upon actually reading the script 
I see that it runs two commands one after the other:

p4 verify -q //depot/...
p4 verify -u -q //depot/...

Is that first verify command really necessary? The output of it gets 
dumped to a log file (which we eventually throw away after not looking 
at it for a couple weeks) but other than that if we run the '-u -q' part 
immediately after that, is it redundant? At other jobs I've only ever 
run that second command on a weekly basis, I just want to be sure I'm 
not missing something.

In the 'p4 help' for verify it also mentions:

p4 verify -q #1,#1
p4 verify -q #head,#head

... to verify the first and head revisions of all files. This leads me 
to believe that it's a good idea to run a plain p4 verify -q after the 
-u -q, but is this (only #1 and #head) significantly faster than running 
it on //...? I suspect it is but wonder if I'll be missing anything, or 
leave my backups at risk, if I don't run it on all revisions ...?

Thanks!

-- 
Matt Janulewicz
Perforce Administrator
Lucasfilm Entertainment Company Limited
matt.janulewicz at lucasfilm.com
415-746-5694