Subversion repository template

[redminele/redminele.git] / subversion / repos / repository_template / hooks / post-revprop-change.tmpl

diff --git a/subversion/repos/repository_template/hooks/post-revprop-change.tmpl b/subversion/repos/repository_template/hooks/post-revprop-change.tmpl
new file mode 100644 (file)
index 0000000..5ea64a2
--- /dev/null
+++ b/subversion/repos/repository_template/hooks/post-revprop-change.tmpl
@@ -0,0 +1,56 @@
+#!/bin/sh\r
+\r
+# POST-REVPROP-CHANGE HOOK\r
+#\r
+# The post-revprop-change hook is invoked after a revision property\r
+# has been added, modified or deleted.  Subversion runs this hook by\r
+# invoking a program (script, executable, binary, etc.) named\r
+# 'post-revprop-change' (for which this file is a template), with the\r
+# following ordered arguments:\r
+#\r
+#   [1] REPOS-PATH   (the path to this repository)\r
+#   [2] REV          (the revision that was tweaked)\r
+#   [3] USER         (the username of the person tweaking the property)\r
+#   [4] PROPNAME     (the property that was changed)\r
+#   [5] ACTION       (the property was 'A'dded, 'M'odified, or 'D'eleted)\r
+#\r
+#   [STDIN] PROPVAL  ** the old property value is passed via STDIN.\r
+#\r
+# Because the propchange has already completed and cannot be undone,\r
+# the exit code of the hook program is ignored.  The hook program\r
+# can use the 'svnlook' utility to help it examine the\r
+# new property value.\r
+#\r
+# On a Unix system, the normal procedure is to have 'post-revprop-change'\r
+# invoke other programs to do the real work, though it may do the\r
+# work itself too.\r
+#\r
+# Note that 'post-revprop-change' must be executable by the user(s) who will\r
+# invoke it (typically the user httpd runs as), and that user must\r
+# have filesystem-level permission to access the repository.\r
+#\r
+# On a Windows system, you should name the hook program\r
+# 'post-revprop-change.bat' or 'post-revprop-change.exe',\r
+# but the basic idea is the same.\r
+# \r
+# The hook program typically does not inherit the environment of\r
+# its parent process.  For example, a common problem is for the\r
+# PATH environment variable to not be set to its usual value, so\r
+# that subprograms fail to launch unless invoked via absolute path.\r
+# If you're having unexpected problems with a hook program, the\r
+# culprit may be unusual (or missing) environment variables.\r
+# \r
+# Here is an example hook script, for a Unix /bin/sh interpreter.\r
+# For more examples and pre-written hooks, see those in\r
+# the Subversion repository at\r
+# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and\r
+# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/\r
+\r
+\r
+REPOS="$1"\r
+REV="$2"\r
+USER="$3"\r
+PROPNAME="$4"\r
+ACTION="$5"\r
+\r
+mailer.py propchange2 "$REPOS" "$REV" "$USER" "$PROPNAME" "$ACTION" /path/to/mailer.conf\r