[p4] change-content triggers and file locks

Tetrick, Cary ctetrick at midway.com
Fri May 11 14:15:05 PDT 2007


I have a trigger script that checks for a few possible problems in
source files during a submission, and blocks it if any are found. 

If the submission is rejected, the files on the server are locked, and
the files on the client are left read only. (This makes sense, given
that it occurs after the file has been transferred to the server - you
don't want files modified in transit.) 

While the files on the server can easily be unlocked, I can't see any
way to keep the client files writable. Has anyone run across this
problem before?



More information about the perforce-user mailing list