moving post-commit with the rest of the scripts for auto-update

[infrastructure.git] / tunings-myplc-devel / post-commit

diff --git a/tunings-myplc-devel/post-commit b/tunings-myplc-devel/post-commit
deleted file mode 100755 (executable)
index 7c45218..0000000
--- a/tunings-myplc-devel/post-commit
+++ /dev/null
@@ -1,73 +0,0 @@
-#!/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"
-
-# using our customized commit email script
-custom=/home/build/1labsvn/infrastructure/tunings-myplc-devel/commit-email.pl
-standard=/usr/share/doc/subversion-1.2.3/tools/hook-scripts/commit-email.pl
-
-if [ -x $custom ] ; then
-  script=$custom
-else
-  script=$standard
-  SUBJECT="$SUBJECT (WARNING : Custom script lost !!!)"
-fi
-
-$script --from "$FROM" -s "$SUBJECT" --size-limit 102400 "$REPOS" "$REV" "$MAILDEST"
-
-#log-commit.py --repository "$REPOS" --revision "$REV"
-
-sudo -u build /plc/devel/data/root/bin/auto-update.sh