[p4] Preventing checkout of entire depot
Chuck Karish
chuck.karish at gmail.com
Fri Apr 4 09:43:03 PDT 2008
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.
>
> Thanks
>
>
> -----Original Message-----
> From: Stephen Vance [mailto:steve at vance.com]
> Sent: Thursday, April 03, 2008 6:14 PM
> To: Nittin chawala
> Cc: Geoff Rowland; perforce-user at perforce.com
> Subject: Re: [p4] Preventing checkout of entire depot
>
>
>
> #1 would prevent submitting the change, but not the checkout itself.
>
> #2 would only limit the scope of the undesirable behavior. You could
> only control it to a certain depth but doing so would introduce many
> wildcards and if deep enough would inhibit their ability to do work. The
>
> cure could be worse than the disease.
>
> I don't think he wants to prevent them from checking the files out if
> they have a good reason. It seems he wants to prevent them from checking
>
> out large quantities of them accidentally.
>
> Also, Geoff, you should try to isolate the cause so that you can report
> it to Perforce.
>
> Steve
>
> Nittin chawala wrote:
> > there are two ways to do this :
> >
> > 1) Write this logic in a trigger ( By this you can prevernt them to
> submit their change )
> > 2) Modify the protection table by removing write access at // level
> for user group. This will not allow them to checkout so a preferred way
> in your case, and you can make seperate group for the people by giving
> write pemission to them whom you think can checkout/submit.
> >
> > --
> > Geoff Rowland <growland at blueomega.com> wrote:
> > Recently we have started to encounter several users accidently
> checking
> > out the entire depot. I believe what happens is they are working in a
> > different window, then P4V gets focused, but they don't realize it,
> and
> > certain keystrokes check out the depot. Is there any way to prevent
> > this? Ideally it would be nice if a message box appeared anytime a
> user
> > tried to check out x amount of files that just said something like
> 'are
> > you sure you really want to do this?'
> >
> >
> >
> > As you can imagine, when dealing with binary+l files, this becomes a
> > huge pain.
> >
> >
> >
> > _______________________________________________
> > perforce-user mailing list - perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >
> >
> > ---------------------------------
> > Bollywood, fun, friendship, sports and more. You name it, we have
> it.
> > _______________________________________________
> > 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
>
--
Chuck Karish karish at well.com (415) 317-0182
More information about the perforce-user
mailing list