[RFC PATCH 1/6] Tell the glossary about core.hooksPath
From: Kenneth Lorber <keni@his.com>
The user manual glossary entry for hooks now knows about core.hooksPath.
Signed-off-by: Kenneth Lorber <keni@his.com>
---
Documentation/glossary-content.txt | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index 090c888335..37147db1bc 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -206,10 +206,12 @@ for a more flexible and robust system to do the same thing.
to optional scripts that allow a developer to add functionality or
checking. Typically, the hooks allow for a command to be pre-verified
and potentially aborted, and allow for a post-notification after the
- operation is done. The hook scripts are found in the
- `$GIT_DIR/hooks/` directory, and are enabled by simply
- removing the `.sample` suffix from the filename. In earlier versions
- of Git you had to make them executable.
+ operation is done. The hook scripts are found in `$GIT_DIR/hooks/`
+ or in any directory specified by the `core.hooksPath` configuration
+ variable. The sample scripts are enabled by simply
+ removing the `.sample` suffix from the filename. In earlier versions
+ of Git you had to make the sample scripts executable manually.
+ Hook scripts must be executable. See linkgit:githooks[5] for details.
[[def_index]]index::
A collection of files with stat information, whose contents are stored
--
2.17.1