From: Miklos Vajna <vmiklos@frugalware.org>
To: gitster@pobox.com
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Markus Heidelberg <markus.heidelberg@web.de>,
git@vger.kernel.org
Subject: [PATCH] githooks documentation: add a note about the +x mode
Date: Wed, 17 Dec 2008 22:29:06 +0100 [thread overview]
Message-ID: <1229549346-17863-1-git-send-email-vmiklos@frugalware.org> (raw)
In-Reply-To: <200812172055.45905.markus.heidelberg@web.de>
In a freshly initialized repo it is only necessary to rename the .sample
hooks, but when using older repos (initialized with older git init)
enabled the +x mode is still necessary - docuement this.
Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---
On Wed, Dec 17, 2008 at 08:55:45PM +0100, Markus Heidelberg <markus.heidelberg@web.de> wrote:
> When you want to learn how to use hooks, you will probably rather read
> githooks(5), where the need for the executable bit is not even
> explicitly mentioned. Maybe it should be added there?
I think so.
Documentation/githooks.txt | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/githooks.txt b/Documentation/githooks.txt
index 5faaaa5..cfdae1e 100644
--- a/Documentation/githooks.txt
+++ b/Documentation/githooks.txt
@@ -20,6 +20,10 @@ directory to trigger action at certain points. When
all disabled. To enable a hook, rename it by removing its `.sample`
suffix.
+NOTE: It is also a requirement for a given hook to be executable.
+However - in a freshly initialized repository - the `.sample` files are
+executable by default.
+
This document describes the currently defined hooks.
applypatch-msg
--
1.6.1.rc1.35.gae26e.dirty
prev parent reply other threads:[~2008-12-17 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 2:59 [PATCH] Documentation: fix description for enabling hooks Markus Heidelberg
2008-12-17 4:13 ` Miklos Vajna
2008-12-17 7:44 ` Johannes Sixt
2008-12-17 14:36 ` Miklos Vajna
2008-12-17 19:55 ` Markus Heidelberg
2008-12-17 21:29 ` Miklos Vajna [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1229549346-17863-1-git-send-email-vmiklos@frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=markus.heidelberg@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).