notes/obliterate/hooks/post-obliterate.tmpl - subversion - Git at Google

 #!/bin/sh

 # POST-OBLITERATE HOOK
 #
 # The post-obliterate hook is invoked after an obliteration.
 # Subversion runs this hook by invoking a program (script, executable,
 # binary, etc.) named 'post-obliterate' (for which this file is a template),
 # with the following ordered arguments:
 #
 #   [1] REPOS-PATH   (the path to this repository)
 #   [2] USER         (the username of the person trying to obliterate)
 #
 #   [STDIN] OBLITERATION-SET   (a list of PATH@REV, one per line)
 #
 # Because the obliteration 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
 # new history of the repository.
 #
 # On a Unix system, the normal procedure is to have 'post-obliterate'
 # invoke other programs to do the real work, though it may do the
 # work itself too.
 #
 # Note that 'post-obliterate' 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-obliterate.bat' or 'post-obliterate.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.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/ and
 # http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/


 REPOS="$1"
 USER="$2"

 # Send out an email notification
 mailer.py obliterate "$REPOS" "$USER" /path/to/mailer.conf
	#!/bin/sh

	# POST-OBLITERATE HOOK
	#
	# The post-obliterate hook is invoked after an obliteration.
	# Subversion runs this hook by invoking a program (script, executable,
	# binary, etc.) named 'post-obliterate' (for which this file is a template),
	# with the following ordered arguments:
	#
	# [1] REPOS-PATH (the path to this repository)
	# [2] USER (the username of the person trying to obliterate)
	#
	# [STDIN] OBLITERATION-SET (a list of PATH@REV, one per line)
	#
	# Because the obliteration 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
	# new history of the repository.
	#
	# On a Unix system, the normal procedure is to have 'post-obliterate'
	# invoke other programs to do the real work, though it may do the
	# work itself too.
	#
	# Note that 'post-obliterate' 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-obliterate.bat' or 'post-obliterate.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.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/ and
	# http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/


	REPOS="$1"
	USER="$2"

	# Send out an email notification
	mailer.py obliterate "$REPOS" "$USER" /path/to/mailer.conf