[svnbook] r5572 committed - trunk/en/book
cmpilato at users.sourceforge.net
cmpilato at users.sourceforge.net
Tue Jan 9 10:51:32 CST 2018
Revision: 5572
http://sourceforge.net/p/svnbook/source/5572
Author: cmpilato
Date: 2018-01-09 16:51:32 +0000 (Tue, 09 Jan 2018)
Log Message:
-----------
Remove <filename> and <command> wrappers for hook script names
(pre-commit, post-unlock, etc.), and refer to them without additional
markup except where referred to as a literal filename or configuration
file section title.
Reported by: wuzhouhui
Modified Paths:
--------------
trunk/en/book/ch03-advanced-topics.xml
trunk/en/book/ch05-repository-admin.xml
trunk/en/book/ch06-server-configuration.xml
Modified: trunk/en/book/ch03-advanced-topics.xml
===================================================================
--- trunk/en/book/ch03-advanced-topics.xml 2018-01-09 12:27:14 UTC (rev 5571)
+++ trunk/en/book/ch03-advanced-topics.xml 2018-01-09 16:51:32 UTC (rev 5572)
@@ -4569,14 +4569,13 @@
<para>Subversion defaults to the <quote>softer</quote>
approach, but still allows administrators to create stricter
enforcement policies through the use of hook scripts. In
- particular, the <filename>pre-lock</filename> and
- <filename>pre-unlock</filename> hooks allow administrators
+ particular, the pre-lock and
+ pre-unlock hooks allow administrators
to decide when lock creation and lock releases are allowed
to happen. Depending on whether a lock already exists,
these two hooks can decide whether to allow a certain user
to break or steal a lock. The
- <filename>post-lock</filename> and
- <filename>post-unlock</filename> hooks are also available,
+ post-lock and post-unlock hooks are also available,
and can be used to send email after locking actions. To
learn more about repository hooks, see
<xref linkend="svn.reposadmin.hooks" />.</para>
Modified: trunk/en/book/ch05-repository-admin.xml
===================================================================
--- trunk/en/book/ch05-repository-admin.xml 2018-01-09 12:27:14 UTC (rev 5571)
+++ trunk/en/book/ch05-repository-admin.xml 2018-01-09 16:51:32 UTC (rev 5572)
@@ -976,7 +976,7 @@
about a commit transaction should be considered read-only.
Instead of modifying a transaction to polish its payload,
simply <emphasis>validate</emphasis> the transaction in
- the <filename>pre-commit</filename> hook and reject the
+ the pre-commit hook and reject the
commit if it does not meet the desired requirements. As a
bonus, your users will learn the value of careful,
compliance-minded work habits.</para>
@@ -1091,8 +1091,8 @@
attempts to change the repository. <command>svnlook</command>
is typically used by the repository hooks for reporting the
changes that are about to be committed (in the case of the
- <command>pre-commit</command> hook) or that were just
- committed (in the case of the <command>post-commit</command>
+ pre-commit hook) or that were just
+ committed (in the case of the post-commit
hook) to the repository. A repository administrator may use
this tool for diagnostic purposes.</para>
@@ -1397,7 +1397,7 @@
<para>Sometimes a user will have an error in her log message (a
misspelling or some misinformation, perhaps). If the
repository is configured (using the
- <literal>pre-revprop-change</literal> hook; see
+ pre-revprop-change hook; see
<xref linkend="svn.reposadmin.hooks" />) to accept changes to
this log message after the commit is finished, the user
can <quote>fix</quote> her log message remotely using
@@ -1425,8 +1425,8 @@
<para>The <command>svnadmin setlog</command> command, by
default, is still bound by the same protections against
modifying unversioned properties as a remote client
- is—the <literal>pre-revprop-change</literal> and
- <literal>post-revprop-change</literal> hooks are still
+ is—the pre-revprop-change and
+ post-revprop-change hooks are still
triggered, and therefore must be set up to accept changes of
this nature. But an administrator can get around these
protections by passing the <option>--bypass-hooks</option>
@@ -1993,7 +1993,7 @@
<para>Another neat trick you can perform with this
<option>--incremental</option> option involves appending to an
existing dump file a new range of dumped revisions. For
- example, you might have a <literal>post-commit</literal> hook
+ example, you might have a post-commit hook
that simply appends the repository dump of the single revision
that triggered the hook. Or you might have a script that runs
nightly to append dump file data for all the revisions that
@@ -2563,7 +2563,7 @@
that only it is doing those things. We accomplish this by
implementing two of the repository event
hooks—pre-revprop-change and start-commit. Our
- <filename>pre-revprop-change</filename> hook script is found
+ pre-revprop-change hook script is found
in <xref
linkend="svn.reposadmin.maint.replication.pre-revprop-change"
/>, and basically verifies that the user attempting the
@@ -2587,7 +2587,7 @@
<para>That covers revision property changes. Now we need to
ensure that only the <literal>syncuser</literal> user is
permitted to commit new revisions to the repository. We do
- this using a <filename>start-commit</filename> hook script
+ this using a start-commit hook script
such as the one in <xref
linkend="svn.reposadmin.maint.replication.start-commit"
/>.</para>
Modified: trunk/en/book/ch06-server-configuration.xml
===================================================================
--- trunk/en/book/ch06-server-configuration.xml 2018-01-09 12:27:14 UTC (rev 5571)
+++ trunk/en/book/ch06-server-configuration.xml 2018-01-09 16:51:32 UTC (rev 5572)
@@ -2302,7 +2302,7 @@
</itemizedlist>
<para>Of course, you might have already set up
- a <filename>pre-commit</filename> hook script to prevent
+ a pre-commit hook script to prevent
commits (see <xref linkend="svn.reposadmin.hooks" />).
But as you read on, you'll see that it's also possible to use
Apache's built-in methods to restrict access in specific
@@ -3808,7 +3808,7 @@
/>.</para>
<para>First, make sure that each slave repository has a
- <filename>pre-revprop-change</filename> hook script which
+ pre-revprop-change hook script which
allows remote revision property changes. (This is
standard procedure for being on the receiving end of
<command>svnsync</command>.) Then log into the master
More information about the svnbook-dev
mailing list