[RFC,1/2] doc: Tell the glossary about core.hooksPath
diff mbox series

Message ID 20200531213757.10752-2-keni@his.com
State New
Headers show
Series
  • update glossary hooks entry
Related show

Commit Message

Kenneth Lorber May 31, 2020, 9:37 p.m. UTC
Signed-off-by: Kenneth Lorber <keni@his.com>
---
 Documentation/glossary-content.txt | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

Patch
diff mbox series

diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index 090c888335..a8490830ff 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -206,10 +206,11 @@  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 them executable.  See linkgit:githooks[5] for details.
 
 [[def_index]]index::
 	A collection of files with stat information, whose contents are stored