mirror of
https://github.com/reactos/reactos.git
synced 2024-09-11 05:12:43 +00:00
Removed file/folder
svn path=/trunk/; revision=12727
This commit is contained in:
parent
b685e5d6be
commit
d57bd697fd
|
@ -1,39 +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.
|
||||
#
|
||||
# Here is an example hook script, for a Unix /bin/sh interpreter:
|
||||
|
||||
REPOS="$1"
|
||||
REV="$2"
|
||||
|
||||
commit-email.pl "$REPOS" "$REV" commit-watchers@example.org
|
||||
log-commit.py --repository "$REPOS" --revision "$REV"
|
|
@ -1,40 +0,0 @@
|
|||
#!/bin/sh
|
||||
|
||||
# POST-REVPROP-CHANGE HOOK
|
||||
#
|
||||
# The post-revprop-change hook is invoked after a revision property
|
||||
# has been changed. Subversion runs this hook by invoking a program
|
||||
# (script, executable, binary, etc.) named 'post-revprop-change'
|
||||
# (for which this file is a template), with the following ordered
|
||||
# arguments:
|
||||
#
|
||||
# [1] REPOS-PATH (the path to this repository)
|
||||
# [2] REV (the revision that was tweaked)
|
||||
# [3] USER (the username of the person tweaking the property)
|
||||
# [4] PROPNAME (the property that was changed)
|
||||
#
|
||||
# Because the propchange 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 property value.
|
||||
#
|
||||
# On a Unix system, the normal procedure is to have 'post-revprop-change'
|
||||
# invoke other programs to do the real work, though it may do the
|
||||
# work itself too.
|
||||
#
|
||||
# Note that 'post-revprop-change' 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-revprop-change.bat' or 'post-revprop-change.exe',
|
||||
# but the basic idea is the same.
|
||||
#
|
||||
# Here is an example hook script, for a Unix /bin/sh interpreter:
|
||||
|
||||
REPOS="$1"
|
||||
REV="$2"
|
||||
USER="$3"
|
||||
PROPNAME="$4"
|
||||
|
||||
propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org
|
|
@ -1,58 +0,0 @@
|
|||
#!/bin/sh
|
||||
|
||||
# PRE-COMMIT HOOK
|
||||
#
|
||||
# The pre-commit hook is invoked before a Subversion txn is
|
||||
# committed. Subversion runs this hook by invoking a program
|
||||
# (script, executable, binary, etc.) named 'pre-commit' (for which
|
||||
# this file is a template), with the following ordered arguments:
|
||||
#
|
||||
# [1] REPOS-PATH (the path to this repository)
|
||||
# [2] TXN-NAME (the name of the txn about to be committed)
|
||||
#
|
||||
# The default working directory for the invocation is undefined, so
|
||||
# the program should set one explicitly if it cares.
|
||||
#
|
||||
# If the hook program exits with success, the txn is committed; but
|
||||
# if it exits with failure (non-zero), the txn is aborted, no commit
|
||||
# takes place, and STDERR is returned to the client. The hook
|
||||
# program can use the 'svnlook' utility to help it examine the txn.
|
||||
#
|
||||
# On a Unix system, the normal procedure is to have 'pre-commit'
|
||||
# invoke other programs to do the real work, though it may do the
|
||||
# work itself too.
|
||||
#
|
||||
# *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT ***
|
||||
# *** FOR REVISION PROPERTIES (like svn:log or svn:author). ***
|
||||
#
|
||||
# This is why we recommend using the read-only 'svnlook' utility.
|
||||
# In the future, Subversion may enforce the rule that pre-commit
|
||||
# hooks should not modify the versioned data in txns, or else come
|
||||
# up with a mechanism to make it safe to do so (by informing the
|
||||
# committing client of the changes). However, right now neither
|
||||
# mechanism is implemented, so hook writers just have to be careful.
|
||||
#
|
||||
# Note that 'pre-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
|
||||
# 'pre-commit.bat' or 'pre-commit.exe',
|
||||
# but the basic idea is the same.
|
||||
#
|
||||
# Here is an example hook script, for a Unix /bin/sh interpreter:
|
||||
|
||||
REPOS="$1"
|
||||
TXN="$2"
|
||||
|
||||
# Make sure that the log message contains some text.
|
||||
SVNLOOK=/usr/local/bin/svnlook
|
||||
$SVNLOOK log -t "$TXN" "$REPOS" | \
|
||||
grep "[a-zA-Z0-9]" > /dev/null || exit 1
|
||||
|
||||
# Check that the author of this commit has the rights to perform
|
||||
# the commit on the files and directories being modified.
|
||||
commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1
|
||||
|
||||
# All checks passed, so allow the commit.
|
||||
exit 0
|
|
@ -1,49 +0,0 @@
|
|||
#!/bin/sh
|
||||
|
||||
# PRE-REVPROP-CHANGE HOOK
|
||||
#
|
||||
# The pre-revprop-change hook is invoked before a revision property
|
||||
# is modified. Subversion runs this hook by invoking a program
|
||||
# (script, executable, binary, etc.) named 'pre-revprop-change' (for which
|
||||
# this file is a template), with the following ordered arguments:
|
||||
#
|
||||
# [1] REPOS-PATH (the path to this repository)
|
||||
# [2] REVISION (the revision being tweaked)
|
||||
# [3] USER (the username of the person tweaking the property)
|
||||
# [4] PROPNAME (the property being set on the revision)
|
||||
#
|
||||
# [STDIN] PROPVAL ** the property value is passed via STDIN.
|
||||
#
|
||||
# If the hook program exits with success, the propchange happens; but
|
||||
# if it exits with failure (non-zero), the propchange doesn't happen.
|
||||
# The hook program can use the 'svnlook' utility to examine the
|
||||
# existing value of the revision property.
|
||||
#
|
||||
# WARNING: unlike other hooks, this hook MUST exist for revision
|
||||
# properties to be changed. If the hook does not exist, Subversion
|
||||
# will behave as if the hook were present, but failed. The reason
|
||||
# for this is that revision properties are UNVERSIONED, meaning that
|
||||
# a successful propchange is destructive; the old value is gone
|
||||
# forever. We recommend the hook back up the old value somewhere.
|
||||
#
|
||||
# On a Unix system, the normal procedure is to have 'pre-revprop-change'
|
||||
# invoke other programs to do the real work, though it may do the
|
||||
# work itself too.
|
||||
#
|
||||
# Note that 'pre-revprop-change' 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
|
||||
# 'pre-revprop-change.bat' or 'pre-revprop-change.exe',
|
||||
# but the basic idea is the same.
|
||||
#
|
||||
# Here is an example hook script, for a Unix /bin/sh interpreter:
|
||||
|
||||
REPOS="$1"
|
||||
REV="$2"
|
||||
USER="$3"
|
||||
PROPNAME="$4"
|
||||
|
||||
if [ "$PROPNAME" = "svn:log" ]; then exit 0; fi
|
||||
exit 1
|
|
@ -1,42 +0,0 @@
|
|||
#!/bin/sh
|
||||
|
||||
# START-COMMIT HOOK
|
||||
#
|
||||
# The start-commit hook is invoked before a Subversion txn is created
|
||||
# in the process of doing a commit. Subversion runs this hook
|
||||
# by invoking a program (script, executable, binary, etc.) named
|
||||
# 'start-commit' (for which this file is a template)
|
||||
# with the following ordered arguments:
|
||||
#
|
||||
# [1] REPOS-PATH (the path to this repository)
|
||||
# [2] USER (the authenticated user attempting to commit)
|
||||
#
|
||||
# The default working directory for the invocation is undefined, so
|
||||
# the program should set one explicitly if it cares.
|
||||
#
|
||||
# If the hook program exits with success, the commit continues; but
|
||||
# if it exits with failure (non-zero), the commit is stopped before
|
||||
# a Subversion txn is created, and STDERR is returned to the client.
|
||||
#
|
||||
# On a Unix system, the normal procedure is to have 'start-commit'
|
||||
# invoke other programs to do the real work, though it may do the
|
||||
# work itself too.
|
||||
#
|
||||
# Note that 'start-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
|
||||
# 'start-commit.bat' or 'start-commit.exe',
|
||||
# but the basic idea is the same.
|
||||
#
|
||||
# Here is an example hook script, for a Unix /bin/sh interpreter:
|
||||
|
||||
REPOS="$1"
|
||||
USER="$2"
|
||||
|
||||
commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1
|
||||
special-auth-check.py --user "$USER" --auth-level 3 || exit 1
|
||||
|
||||
# All checks passed, so allow the commit.
|
||||
exit 0
|
Loading…
Reference in a new issue