[p4] Preventing checkout of entire depot

[Jamison, Shawn]

You want to remove write access at the //... Level anyway.  
I think write access at //... Would allow the auto creation of user
accounts and that's not a good thing. 


-Shawn Jamison>
Ciena Corp.
Perforce Admin

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Nittin chawala
Sent: Thursday, April 03, 2008 11:38 AM
To: Geoff Rowland; perforce-user at perforce.com
Subject: Re: [p4] Preventing checkout of entire depot

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