Difference: CVS (4 vs. 5)

Revision 52007-09-27 - KevinLeytonBrown

  META TOPICPARENT 
 name="SunGridEngine"
- META TOPICPARENT
+ name="SunGridEngine"
-<
<
+ Permissions 

Users of CVS have to take some one-time steps so that the permissions of files the commit will be correct. (Otherwise, other uses will be unable to modify or even update files that such users have created.)
 

 Set up permissions so all files are group writable. All directories need to be group rwx.  (as far as I know, this is already done in /ai/kevinlb/cvs, for the group klb). 
  Copy the file from /hooks/post-commit.tmpl to /hooks/post-commit and add the lines:
->
>
+CVS"> Using CVS
-<
<
+ chgrp -R  
  chmod -R g+rwx
->
>
+This page is part of the EmpiricalAlgorithmics web.
-<
<
+Each student will have to do this so that whenever they commit files, the files will get chgrp'ed and chmod'ed.

These instructions come from Tim (timkl@csDELETEthisTEXT.ubc.ca); please direct questions to him.

 Permissions redux
->
>
+ Permissions
-<
<
+The above didn't seem to always work. Here's something else from Sean Godel:
->
>
+Here's something from Sean Godel:
-<
<
+Hi Kevin, so doing more research into this I discovered a few things.
 If the CVS client is configured to go through okanagan then group
inheritance is preserved. If it goes through cascade group inheritance
is preserved for the first directory created but nothing after that.
  CVS in Windows
-<
<
+A good Windows CVS client that integrates with Explorer is TortoiseCVS.  It's open-source.
->
>
+A good Windows CVS client that integrates with Explorer is TortoiseCVS.  It's open-source. Use Okanagan as your server, and connect using SSH.
  Setting up a public/private key pair so that you don't have to authenticate every time

View topic | History: r10 < r9 < r8 < r7 | More topic actions...