[svnbook] r5974 committed - trunk/en/book/ref-reposhooks.xml
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Sun Sep 1 05:45:17 CDT 2019
Revision: 5974
http://sourceforge.net/p/svnbook/source/5974
Author: wuzhouhui
Date: 2019-09-01 10:45:13 +0000 (Sun, 01 Sep 2019)
Log Message:
-----------
* en/book/ref-reposhooks.xml
Remove <literal> wrapper for hooks, follow up r5572.
Modified Paths:
--------------
trunk/en/book/ref-reposhooks.xml
Modified: trunk/en/book/ref-reposhooks.xml
===================================================================
--- trunk/en/book/ref-reposhooks.xml 2019-09-01 10:07:00 UTC (rev 5973)
+++ trunk/en/book/ref-reposhooks.xml 2019-09-01 10:45:13 UTC (rev 5974)
@@ -158,7 +158,7 @@
<refsect1>
<title>Description</title>
- <para>The <literal>pre-commit</literal> hook is run just
+ <para>The pre-commit hook is run just
before a commit transaction is promoted to a new revision.
Typically, this hook is used to protect against commits that
are disallowed due to content or location (e.g., your
@@ -166,7 +166,7 @@
include a ticket number from the bug tracker, or that the
incoming log message is nonempty).</para>
- <para>If the <literal>pre-commit</literal> hook program
+ <para>If the pre-commit hook program
returns a nonzero exit value, the commit is aborted, the
commit transaction is removed, and anything printed to
<filename>stderr</filename> is marshalled back to the client.</para>
@@ -236,7 +236,7 @@
<refsect1>
<title>Description</title>
- <para>The <literal>post-commit</literal> hook is run after the
+ <para>The post-commit hook is run after the
transaction is committed and a new revision is created. Most
people use this hook to send out descriptive emails about
the commit or to notify some other tool (such as an issue
@@ -243,7 +243,7 @@
tracker) that a commit has happened. Some configurations
also use this hook to trigger backup processes.</para>
- <para>If the <literal>post-commit</literal> hook returns a
+ <para>If the post-commit hook returns a
nonzero exit status, the commit <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
@@ -310,7 +310,7 @@
<refsect1>
<title>Description</title>
- <para>The <literal>pre-revprop-change</literal> hook is run
+ <para>The pre-revprop-change hook is run
immediately prior to the modification of a revision property
when performed outside the scope of a normal commit. Unlike
the other hooks, the default state of this one is to deny
@@ -318,7 +318,7 @@
return a zero exit value before a revision property
modification can happen.</para>
- <para>If the <literal>pre-revprop-change</literal> hook doesn't
+ <para>If the pre-revprop-change hook doesn't
exist, isn't executable, or returns a nonzero exit value, no
change to the property will be made, and anything printed
to <filename>stderr</filename> is marshalled back to the
@@ -396,17 +396,17 @@
<refsect1>
<title>Description</title>
- <para>The <literal>post-revprop-change</literal> hook is run
+ <para>The post-revprop-change hook is run
immediately after the modification of a revision property
when performed outside the scope of a normal commit. As you can
derive from the description of its counterpart, the
- <literal>pre-revprop-change</literal> hook, this hook will
+ pre-revprop-change hook, this hook will
not run at all unless
- the <literal>pre-revprop-change</literal> hook is
+ the pre-revprop-change hook is
implemented. It is typically used to send email
notification of the property change.</para>
- <para>If the <literal>post-revprop-change</literal> hook returns a
+ <para>If the post-revprop-change hook returns a
nonzero exit status, the change <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
@@ -483,7 +483,7 @@
<refsect1>
<title>Description</title>
- <para>The <literal>pre-lock</literal> hook runs whenever
+ <para>The pre-lock hook runs whenever
someone attempts to lock a path. It can be used to prevent
locks altogether or to create a more complex policy
specifying exactly which users are allowed to lock
@@ -491,7 +491,7 @@
it can also decide whether a user is allowed
to <quote>steal</quote> the existing lock.</para>
- <para>If the <literal>pre-lock</literal> hook program returns
+ <para>If the pre-lock hook program returns
a nonzero exit value, the lock action is aborted and
anything printed to <filename>stderr</filename> is
marshalled back to the client.</para>
@@ -503,7 +503,7 @@
unexpected output sent to standard output.</para>
<warning>
- <para>If the <literal>pre-lock</literal> script takes
+ <para>If the pre-lock script takes
advantage of lock token dictation feature, the
responsibility of generating a <emphasis>unique</emphasis>
lock token falls to the script itself. Failure to
@@ -576,11 +576,11 @@
<refsect1>
<title>Description</title>
- <para>The <literal>post-lock</literal> hook runs after one or
+ <para>The post-lock hook runs after one or
more paths have been locked. It is typically used to send
email notification of the lock event.</para>
- <para>If the <literal>post-lock</literal> hook returns a
+ <para>If the post-lock hook returns a
nonzero exit status, the lock <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
@@ -647,7 +647,7 @@
<refsect1>
<title>Description</title>
- <para>The <literal>pre-unlock</literal> hook runs whenever
+ <para>The pre-unlock hook runs whenever
someone attempts to remove a lock on a file. It can be used
to create policies that specify which users are allowed to
unlock particular paths. It's particularly important for
@@ -656,7 +656,7 @@
is more than a week old? These sorts of things can be
decided and enforced by the hook.</para>
- <para>If the <literal>pre-unlock</literal> hook program
+ <para>If the pre-unlock hook program
returns a nonzero exit value, the unlock action is aborted
and anything printed to <filename>stderr</filename> is marshalled back to the
client.</para>
@@ -725,11 +725,11 @@
<refsect1>
<title>Description</title>
- <para>The <literal>post-unlock</literal> hook runs after one
+ <para>The post-unlock hook runs after one
or more paths have been unlocked. It is typically used to
send email notification of the unlock event.</para>
- <para>If the <literal>post-unlock</literal> hook returns a
+ <para>If the post-unlock hook returns a
nonzero exit status, the unlock <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
More information about the svnbook-dev
mailing list