[p4] Preventing checkout of entire depot

[Robert Cowham]

A couple of alternatives:

- set maxresults/maxscanrows to avoid this sort of thing

- create a suitable default client workspace (via a trigger) so that anyone
starting from scratch get's a small part of the repository and must
explicitly select what they want.

The nag emails are good for those who escaped the implementation of the
second version. As a backup you can do things like look for old clients, and
consider more drastic options such as removing (with spec depot backup) or
forcible editing them.

Robert

> We have nag scripts that send email to owners of clients that 
> still have the default view, which maps our whole code base.  
> If the client view is reasonable no accidental sequence of 
> keystrokes will cause a problem.
> 
> On Thu, Apr 3, 2008 at 4:53 PM, Geoff Rowland 
> <growland at blueomega.com> wrote:
> > Yes, this is correct, I want to prevent users from 
> accidently checking  
> > out large quantities of files.  So I would not want them to 
> be able to  
> > check out the entire Branch, for example, without 
> confirmation.  Most  
> > users are in groups that have proper protections set up so 
> they would  
> > not be able to check out the entire depot - I misspoke in 
> my original  
> > email.