In the glossary entry for hooks: - don't discuss renaming the sample hooks - don't discuss the need to make the sample hooks executable as the existing wording is too specific: it implies only the sample hooks need to be executable and the need to make scripts executable is already discussed near the top of hooks(5). Signed-off-by: Kenneth Lorber <keni@xxxxxxx> --- Documentation/glossary-content.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt index a8490830ff..d96b25bef3 100644 --- a/Documentation/glossary-content.txt +++ b/Documentation/glossary-content.txt @@ -208,9 +208,8 @@ for a more flexible and robust system to do the same thing. and potentially aborted, and allow for a post-notification after the 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. + configuration variable. + See linkgit:githooks[5] for details. [[def_index]]index:: A collection of files with stat information, whose contents are stored -- 2.17.1
