os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace-only cleanup of last commit.

Browse source
This commit is contained in:
Tony Finch 2002-07-25 17:22:43 +00:00
parent 8c6d42bc3d
commit 62bde5a555
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13707
1 changed files with 39 additions and 40 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

79
en_US.ISO8859-1/articles/cvs-freebsd/article.sgml
View file

@ -181,8 +181,9 @@
<listitem>
<para><filename>checkoutlist</filename> - this files lists all
files under control of <application>CVS</application> in this
directory, apart from the standard ones created by <literal>cvs init</literal>. You should edit this to remove some FreeBSD-specific
files.</para>
directory, apart from the standard ones created by
<literal>cvs init</literal>. You should edit this to remove
some FreeBSD-specific files.</para>
</listitem>
<listitem>
@ -194,12 +195,13 @@
<listitem>
<para><filename>commitcheck</filename> - this script is invoked
directly from <application>CVS</application>. It first checks if
the committer has access to the specified part of the tree using <filename>cvs_acls.pl</filename>, and
then runs <filename>commit_prep.pl</filename> for the various
pre-commit checks. If those are OK, <application>CVS</application>
will allow the commit to proceed. You should not have to touch
this file.</para>
directly from <application>CVS</application>. It first checks
if the committer has access to the specified part of the tree
using <filename>cvs_acls.pl</filename>, and then runs
<filename>commit_prep.pl</filename> for the various pre-commit
checks. If those are OK, <application>CVS</application> will
allow the commit to proceed. You should not have to touch this
file.</para>
</listitem>
<listitem>
@ -262,27 +264,25 @@
<listitem>
<para><filename>exclude</filename> - this file lists regular
expressions that are used by <filename>commit_prep.pl</filename> to determine files which cannot contain a
revision header. In the FreeBSD setup, all files under revision
control need to have a revision header (like
&dollar;FreeBSD&dollar;). All filenames that match one of the lines
in this file are exempted from this check. You should add
expressions to this file as you checkin files that cannot have a
revision header. For the purpose of installing the scripts, it
may be best to exclude <filename>CVSROOT/</filename> from header
checks.</para>
expressions that are used by <filename>commit_prep.pl</filename>
to determine files which cannot contain a revision header. In the
FreeBSD setup, all files under revision control need to have a
revision header (like &dollar;FreeBSD&dollar;). All filenames that
match one of the lines in this file are exempted from this check.
You should add expressions to this file as you checkin files that
cannot have a revision header. For the purpose of installing the
scripts, it may be best to exclude <filename>CVSROOT/</filename>
from header checks.</para>
</listitem>
<listitem>
<para><filename>log_accum.pl</filename> - this is a script that
takes the log message as provided by the
<filename>logcheck</filename> script, and appends it to a log file
in the repository for backup purposes. It also handles mailing out a
message to an email address you provide (in
<filename>cfg_local.pm</filename>). It hooks into
<application>CVS</application> via
<filename>loginfo</filename>. You should not have to touch
this file.</para>
<para><filename>log_accum.pl</filename> - this is a script that takes
the log message as provided by the <filename>logcheck</filename>
script, and appends it to a log file in the repository for backup
purposes. It also handles mailing out a message to an email address
you provide (in <filename>cfg_local.pm</filename>). It hooks into
<application>CVS</application> via <filename>loginfo</filename>.
You should not have to touch this file.</para>
</listitem>
<listitem>
@ -308,8 +308,7 @@
<para><filename>loginfo</filename> - this file is used by
<application>CVS</application> to control where log
information is sent; <filename>log_accum.pl</filename> hooks
in here. You should not have to touch this
file.</para>
in here. You should not have to touch this file.</para>
</listitem>
<listitem>
@ -363,33 +362,33 @@
<listitem>
<para><filename>taginfo</filename> - this file maps tag operations
on repository directories to access control scripts such as
<filename>tagcheck</filename>. You should not
have to touch this file.</para>
<filename>tagcheck</filename>. You should not have to touch this
file.</para>
</listitem>
<listitem>
<para><filename>unwrap</filename> - this script can be used to
automatically <quote>unwrap</quote> binary files (see
<filename>cvswrappers</filename>) on checkout. It is not used in the
current FreeBSD setup because the functionality it hooks into
doesn't work well with remote commits. You should not have to touch this
file.</para>
<filename>cvswrappers</filename>) on checkout. It is not used in
the current FreeBSD setup because the functionality it hooks into
doesn't work well with remote commits. You should not have to
touch this file.</para>
</listitem>
<listitem>
<para><filename>verifymsg</filename> - this file maps repository
directories to post processor scripts of log messages such as
<filename>logcheck</filename>. You should
not have to touch this file.</para>
<filename>logcheck</filename>. You should not have to touch
this file.</para>
</listitem>
<listitem>
<para><filename>wrap</filename> - this script can be used to
automatically <quote>wrap</quote> binary files (see
<filename>cvswrappers</filename>) on checkin. It is not used in the
current FreeBSD setup because the functionality it hooks into
doesn't work well with remote commits. You should not have to touch this
file.</para>
<filename>cvswrappers</filename>) on checkin. It is not used
in the current FreeBSD setup because the functionality it
hooks into doesn't work well with remote commits. You should
not have to touch this file.</para>
</listitem>
</itemizedlist>
</sect2>