
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
80
|
Chapter 5: Repository Administration
remotely modify revision properties at all unless this hook is implemented for
your repository.
This hook runs just before such a modification is made to the repository. The
repository passes four arguments to this hook: the path to the repository, the
revision on which the to-be-modified property exists, the authenticated user-
name of the person making the change, and the name of the property itself.
post-revprop-change
As mentioned earlier, this hook is the counterpart of the pre-revprop-change
hook. In fact, for the sake of paranoia this script will not run unless the pre-
revprop-change hook exists. When both of these hooks are present, the post-
revprop-change hook runs just after a revision property has been changed, and is
typically used to send an email containing the new value of the changed prop-
erty. The repository passes four arguments to this hook: the path to the reposi-
tory, the revision on which the property exists, the authenticated username of
the person making the change, and the name of the property itself.
The Subversion distribution includes a
propchange-email.pl script (located in
the tools/hook-scripts/ directory of the Subversion source tree) that can be used
to send email with (and/or append to a log file) the details ...