[svnbook commit] r3054 - trunk/src/en/book
fitz
noreply at red-bean.com
Sun May 4 00:38:19 CDT 2008
Author: fitz
Date: Sun May 4 00:38:19 2008
New Revision: 3054
Log:
Explain that post-* hook STDERR is marshalled back to the client.
Patch from Mark E. Hamilton (mhamilt at sandia.gov), with some slight
tweaks.
This fixes issue #110.
* src/en/book/ch09-reference.xml: Tell the truth about post-* hook
STDERR output.
Modified:
trunk/src/en/book/ch09-reference.xml
Modified: trunk/src/en/book/ch09-reference.xml
==============================================================================
--- trunk/src/en/book/ch09-reference.xml (original)
+++ trunk/src/en/book/ch09-reference.xml Sun May 4 00:38:19 2008
@@ -8303,9 +8303,12 @@
tracker) that a commit has happened. Some configurations
also use this hook to trigger backup processes.</para>
- <para>The output from and the exit value returned by the
- <literal>post-commit</literal> hook program are
- ignored.</para>
+ <para>If the <literal>post-commit</literal> 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
+ to <literal>STDERR</literal> will be marshalled back to the
+ client, making it easier to diagnose hook failures.</para>
</refsect1>
@@ -8431,9 +8434,12 @@
implemented. It is typically used to send email
notification of the property change.</para>
- <para>The output from, and exit value returned by, the
- <literal>post-revprop-change</literal> hook program is
- ignored.</para>
+ <para>If the <literal>post-revprop-change</literal> 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
+ to <literal>STDERR</literal> will be marshalled back to the
+ client, making it easier to diagnose hook failures.</para>
</refsect1>
@@ -8555,9 +8561,12 @@
more paths has been locked. It is typically used to send
email notification of the lock event.</para>
- <para>The output from and exit value returned by
- the <literal>post-lock</literal> hook program is
- ignored.</para>
+ <para>If the <literal>post-lock</literal> 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
+ to <literal>STDERR</literal> will be marshalled back to the
+ client, making it easier to diagnose hook failures.</para>
</refsect1>
@@ -8670,9 +8679,12 @@
or more paths has been unlocked. It is typically used to
send email notification of the unlock event.</para>
- <para>The output from and exit value returned by, the
- <literal>post-unlock</literal> hook program is
- ignored.</para>
+ <para>If the <literal>post-unlock</literal> 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
+ to <literal>STDERR</literal> will be marshalled back to the
+ client, making it easier to diagnose hook failures.</para>
</refsect1>
More information about the svnbook-dev
mailing list