[p4] How can I prevent a user from using "accept mine" during resolution

[Tony Andrew Kennah]

It may be possible but its not a good idea.  Instead "name" the culprits (or 
whip them) upon detection...

The problem, as you rightly question, is catching this type of breach. 
Continuous Integration with a twist of Test-Driven Development help with 
detection, digging around in Perforce after detection may force you to get 
the whips out.

You use branching or a moving label to protect against breaches.

Tony



> Alok Narula wrote:
>> Hi,
>>
>>
>>
>> In my company I'm finding that some developers don't take the pain of
>> resolving a file when the file they're trying to submit is earlier
>> than the depot version. These guys select "accept mine" when Perforce
>> prompts them to resolve a file, and consequently overwrite the latest
>> revision with their old revision, which sometimes is many revisions
>> older than the latest revision.
>>
>>
>>
>> I would like to know how I can prevent a user from using "accept mine"
>> during resolution? I was thinking of writing a trigger but I don't see
>> any argument that captures the return value of the p4 resolve command.
>>
>>
>>
>> Alok
>>
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>>
>
> -- 
> Stephen Vance
> www.vance.com
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>