[p4] Accidental checkout

G Barthelemy gb.perforce at googlemail.com
Tue Aug 29 03:44:49 PDT 2006


On 8/28/06, Jeff Desharnais <jdesharnais at maddocsoftware.com> wrote:
> This causes major problems for our development team because they are
> forced to wait a very long time while every file is reverted.
>
> Have any of you ever come across this problem before or have any insight
> to this?

One way of preventing the accidental (or not) checkout of an entire
depot is to setup a "form-save" trigger on the client command that
validates client specs as they are created / edited, and prevents the
mapping of an entire depot in the first place.

I can't think of many situations where mapping a whole depot would be
of much use.

The trigger, for instance, could be looking for the string
"//depot/... " in the View: section of the client, and if matched
print a message asking the user to narrow down her mapping of the
depot.

I realise this doesn't cure the <CTRL-E> problem, but at least it may
lessen the impact.
--
Guillaume


More information about the perforce-user mailing list