From acf48a91eb8cdcd3d6ccb8d9bac661bbca5442e2 Mon Sep 17 00:00:00 2001
From: build <build@41d37cc5-eb28-0410-a9bf-d37491348ade>
Date: Mon, 12 Mar 2007 14:15:21 +0000
Subject: [PATCH] the post-commit hook for the subversion repository

---
 tunings-myplc-devel/post-commit | 60 +++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)
 create mode 100755 tunings-myplc-devel/post-commit

diff --git a/tunings-myplc-devel/post-commit b/tunings-myplc-devel/post-commit
new file mode 100755
index 0000000..689da9f
--- /dev/null
+++ b/tunings-myplc-devel/post-commit
@@ -0,0 +1,60 @@
+#!/bin/sh
+
+# POST-COMMIT HOOK
+#
+# The post-commit hook is invoked after a commit.  Subversion runs
+# this hook by invoking a program (script, executable, binary, etc.)
+# named 'post-commit' (for which this file is a template) with the 
+# following ordered arguments:
+#
+#   [1] REPOS-PATH   (the path to this repository)
+#   [2] REV          (the number of the revision just committed)
+#
+# The default working directory for the invocation is undefined, so
+# the program should set one explicitly if it cares.
+#
+# Because the commit has already completed and cannot be undone,
+# the exit code of the hook program is ignored.  The hook program
+# can use the 'svnlook' utility to help it examine the
+# newly-committed tree.
+#
+# On a Unix system, the normal procedure is to have 'post-commit'
+# invoke other programs to do the real work, though it may do the
+# work itself too.
+#
+# Note that 'post-commit' must be executable by the user(s) who will
+# invoke it (typically the user httpd runs as), and that user must
+# have filesystem-level permission to access the repository.
+#
+# On a Windows system, you should name the hook program
+# 'post-commit.bat' or 'post-commit.exe',
+# but the basic idea is the same.
+# 
+# The hook program typically does not inherit the environment of
+# its parent process.  For example, a common problem is for the
+# PATH environment variable to not be set to its usual value, so
+# that subprograms fail to launch unless invoked via absolute path.
+# If you're having unexpected problems with a hook program, the
+# culprit may be unusual (or missing) environment variables.
+# 
+# Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in
+# the Subversion repository at
+# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
+# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
+
+
+REPOS="$1"
+REV="$2"
+MAILDEST="onelab-svn@one-lab.org"
+#FROM="$MAILDEST"
+FROM="$(id -un)@svn.one-lab.org"
+SUBJECT="svn.one-lab.org - check in:"
+
+/usr/share/doc/subversion-1.2.3/tools/hook-scripts/commit-email.pl \
+        --from "$FROM" \
+        -s "$SUBJECT" \
+        "$REPOS" "$REV" "$MAILDEST"
+
+#log-commit.py --repository "$REPOS" --revision "$REV"
+
+sudo -u build /plc/devel/data/root/bin/auto-update.sh
-- 
2.43.0