[PATCH] README files in 'hook-scripts' directories

[Mathias Weinert <ma...@gfa-net.de>]

Hi,

I just noticed that contrib/hook-scripts/README and
tools/hook-scripts/README are a bit out of date.

Please check the description of 'commit-email.rb'
as I am not sure what this script exactly does.

BTW, why are there two locations were hook scripts are
stored? Wouldn't it be better to store them at only one
place?

Mathias

[[[
* contrib/hook-scripts/README
  pre-lock-require-needs-lock.py and svn2rss.py added

* tools/hook-scripts/README
  commit-email.rb, verify-po.py and path to mailer.py added
]]]

--- contrib/hook-scripts/README.orig    2005-07-18 17:21:38.000000000 +0200
+++ contrib/hook-scripts/README 2005-11-30 09:29:38.700042000 +0100
@@ -20,5 +20,11 @@
    5. pre-commit-check.py
       Template for writing pre-commit checks with the python bindings.

+   6. pre-lock-require-needs-lock.py
+      This script verifies that the path a user is attempting to lock
+      has the 'svn:needs-lock' property set on it.
+
+   7. svn2rss.py
+      Generates a RSS 2.0 file containing commit information.

 $Id: README 15358 2005-07-18 15:21:38Z martinto $
--- tools/hook-scripts/README.orig      2004-03-28 01:25:38.000000000 +0100
+++ tools/hook-scripts/README   2005-11-30 09:48:32.273845600 +0100
@@ -6,7 +6,10 @@
       from `repository/hooks/post-commit'.  Run the script with no
       arguments for usage.

-   2. mailer.py, mailer.conf.example
+   2. commit-email.rb
+      Send commit emails.
+
+   3. mailer/mailer.py, mailer/mailer.conf.example
       Uses the Python/SWIG bindings to directly query the repository
       about the changes made by a particular revision.  The program
       uses a configuration file for basic setup and to fine-tune where
@@ -15,19 +18,23 @@
       smarter with binary files, and it streams its output into the
       mailer (to avoid in-memory buffering).

-   3. commit-access-control.pl, commit-access-control.cfg.example
+   4. commit-access-control.pl, commit-access-control.cfg.example
       Uses the `svnlook' program to check if the user who submitted
       the commit has appropriate rights to perform the commit on all
       the modified files and directories using the permissions
       specified in the configuration file.

-   4. svnperms.py, svnperms.conf.example
+   5. svnperms.py, svnperms.conf.example
       Similar to commit-access-control.pl, but uses a different
       syntax.  Run 'svnperms.py -h' for usage.

-   5. propchange-email.pl
+   6. propchange-email.pl
       Uses the `svnlook' program to send revision property change notice
       emails.  Invoke it from `repository/hook/post-revprop-change'.  Run
       the script with no arguments for usage.

+   7. verify-po.py
+      Checks whether the contents of PO files committed to the repository
+      are encoded in UTF-8.
+
 $Id: README 9219 2004-03-28 00:25:38Z kfogel $

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org