diff --git a/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml b/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml index b0425d3b..d16edf73 100644 --- a/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml +++ b/LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml @@ -2,11 +2,11 @@ - - + @@ -17,7 +17,7 @@ - + @@ -30,6 +30,7 @@ + @@ -46,7 +47,7 @@ - + @@ -66,6 +67,13 @@ + + +0.7 +2005-10-15 +vv +A bunch of minor fixes as suggested by readers. + 0.6 @@ -166,14 +174,14 @@ deploying &CVSAB; in his or her organization. Some of the popular -The &CVS; site where +The &CVS; site where current informaton about CVS is available. Including the &CVSAB; manual. +url="http://ximbiot.com/cvs/wiki/index.php?title=Cederqvist">&CVSAB; manual. -Karl Fogel's book Open Source Development with -CVS has GPL'd sections available online. +Karl Fogel's book, Open Source Development with +CVS is available online. @@ -218,7 +226,7 @@ document, and would like to be notified of any plans to redistribute the same. the concepts, examples and other content at your own risk. As this is a new edition of this document, there may be errors and inaccuracies that may of course be damaging to your system. Proceed with caution, and although this is -highly unlikely, the author(s) do not take any responsibility for that. +highly unlikely, the author(s) do not take any responsibility whatsoever. All copyrights are held by their respective owners, unless specifically @@ -236,19 +244,19 @@ major installation and backups at regular intervals. New Versions - The version number of this document is &DOCVERSION;. + This document is Version : &DOCVERSION;. - The latest version of this document can be obtained from + The latest version of this document can be obtained from (In the order of latest version availability) -My website +My website -The linux documentation project +The linux documentation project @@ -339,6 +347,10 @@ additions, comments and criticisms to the following email address : + + + + @@ -538,13 +550,11 @@ name will ensure that the sandboxes are kept up to date. §ion2-workinside; -The sandbox can be thought of as a controlled area within which -&CVSAB; can track for changes made to the various source files. Files -belonging to other developers will be automatically updated by &CVSAB;. -Thus the developer who lives within the sandbox will stand to gain a lot of -benefits of concurrent development. This benefit cannot be achieved for -work done outside a sandbox. - +The sandbox can be thought of as a controlled area within which &CVSAB; + can track for changes made to the various source files. Files belonging to + other developers will be automatically updated by &CVSAB; in the developer's + sandbox. Thus the developer who lives within the sandbox will stand to gain + a lot of benefits of concurrent development. @@ -593,6 +603,21 @@ them. Thus, audit trail can be established if necessary. configuration. + + §ion2-accesscontrol; + + One of the important questions that I have been asked time and again is the + ability to have access control for files/folders/branches etc., within + the &CVSAB; repository for various users. Unfortunately &CVSAB; does not + come with a built in Access control capability but it does support a + rudimentary form of access control through the readers/writers files in + the CVSROOT repository. I have put together a set of scripts that use + the readers/writers files to provide a slightly useable version of access + control. This is available at http://cvspermissions.sarovar.org + as an &OPENSOURCE; project. Feel free to use it and let me know how it + works for you. + §ion2-scripting;