LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Changed my email address, Fixed bug in URL, general cleanup. Ready for publishing as 0.3

This commit is contained in:
vivekv 2001-12-06 01:01:56 +00:00
parent 59f652294d
commit 787c9ad4b9
1 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
LDP/ref/docbook/CVS-BestPractices/CVS-BestPractices.sgml
View File

@ -12,7 +12,7 @@
<!ENTITY CVSAB "CVS">
<!ENTITY SCMAB "SCM">
<!ENTITY SCM "Software configuration management">
<!ENTITY MYEMAIL "vivekv at users.sourceforge.net">
<!ENTITY MYEMAIL "vivekv at yahoo.com">
]>
@ -25,16 +25,16 @@
<firstname>Vivek</firstname>
<surname>Venugopalan</surname>
<affiliation>
<address><email>vivekv at users.sourceforge.net</email></address></affiliation>
<address><email>&MYEMAIL;</email></address></affiliation>
</author>
<revhistory>
<revision>
<revnumber>0.3</revnumber>
<date>2001-12-01</date>
<date>2001-12-06</date>
<authorinitials>vv</authorinitials>
<revremark>Grammatical errors</revremark>
<revremark>Grammatical errors cleanup</revremark>
</revision>
<revision>
@ -90,6 +90,12 @@ verbally as a bunch of <quote>gotchas</quote> on &CVSAB;, it was time to put
down on paper some of the best practices that will work well for
&CVSAB; based projects. </para>
<note>
<para>This paper is not an introduction to &CVSAB; and its usage. There are
excellent articles available on the net for the same. This paper assumes
that the reader is familiar with &CVSAB; commands and is looking at
deploying &CVSAB; in his or her organization.</para>
</note>
<!-- Section2: copyright -->
<sect2 id="copyright">
@ -159,7 +165,7 @@ major installation and backups at regular intervals. </para> </sect2>
</listitem>
<listitem>
<para>
<ulink url="http://www.linuxdoc.org/doc.html">The linux documentation project</ulink>
<ulink url="http://www.linuxdoc.org/doc.html#cvs_bestpractices">The linux documentation project</ulink>
</para>
</listitem>
</orderedlist>
@ -361,7 +367,7 @@ find the &CVSAB; command-line interface daunting. The adoption and usage of
&CVSAB; can be improved by using GUI tools for &CVSAB; clients. </para>
<para> GUI tools for &CVSAB; are available at <ulink
url="www.cvsgui.org">www.cvsgui.org</ulink>. GUI interfaces are available for
url="http://www.cvsgui.org">http://www.cvsgui.org</ulink>. GUI interfaces are available for
most of the popular platforms (Windows, Mac and Linux). In addition, on the
Windows platform there is an <acronym>SCC</acronym> extension that allows
integration of &CVSAB; as the configuration control tool with popular