[p4] Locked files after a failed submit

[Stephen Vance]

It's a feature of failed submissions in general. One of the most 
frequent causes of failed submissions is unresolved changes. This makes 
sure that the revisions against which you are resolving (in the case of 
parallel development) doesn't change further while you are performing 
the resolve.

Steve

Melissa Kacher wrote:
> Change-submit and change-content triggers both leave all of the files in
> the change list locked when they fail. 
> Does anybody know why that is? Or why it is desirable behavior? I'd like
> to understand this before I go off and try to get around it. I'm
> thinking that unlocking files while still in the trigger might not work,
> or might do bad things. But I don't want the files left locked when a
> trigger fails. Who knows how long it will take the user to fix the
> problem and re-submit. In the mean time, everyone else is prevented from
> submitting those files.
> Any ideas out there? I saw a thread about this a month ago, but I don't
> see that any conclusion was reached.
>
>
> Thanks,
> Melissa
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>