[p4] A trigger change-submit deadlock

[Rex Tener]

At 01:32 PM 9/7/2007, Matthew Janulewicz wrote:
>Not to sound like an idiot or to insinuate anything, but you're sure
>it's a change-submit and not a change-commit trigger?

If you just need to access the changelist description, then a 
change-submit will work.  From the Perforce Sys Admin Manual:

     <http://www.perforce.com/perforce/doc.072/manuals/p4sag/06_scripting.html#1060107>

     change-submit: Execute a changelist trigger after changelist 
creation, but before
                    file transfer. Trigger may not access file contents.

>And in either case a rejected submit does not create a numbered changelist.

I was surprised by this too, but the Perforce user guide indicates 
that a failed submit for the default changelist creates a numbered changelist.

     <http://www.perforce.com/perforce/doc.072/manuals/p4guide/04_files.html#1055937> 


     If an error occurs when you submit the default changelist, 
Perforce creates a numbered
     changelist containing the files you attempted to submit. You 
must then fix the problems
     and submit the numbered changelist using the -c flag.

Rex