From: Markus Heidelberg <markus.heidelberg@web.de>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix description for enabling hooks
Date: Wed, 17 Dec 2008 20:55:45 +0100 [thread overview]
Message-ID: <200812172055.45905.markus.heidelberg@web.de> (raw)
In-Reply-To: <20081217143627.GB5691@genesis.frugalware.org>
Miklos Vajna, 17.12.2008:
> On Wed, Dec 17, 2008 at 08:44:40AM +0100, Johannes Sixt <j.sixt@viscovery.net> wrote:
> > > This is true, but having the executable bit is necessary as well. I
> > > think it would be better to just append this requirement instead of
> > > replacing the old one with this.
> >
> > Markus's proposed new wording is correct because the .sample hooks *are*
> > already executable.
>
> I thought about the following situation: The user reads the
> documentation while working in an older repo (initialized a few versions
> ago). S/he sees that the .sample suffix is already missing, so s/he
> assumes that the hook is already active. Which is not true, because the
> +x bit is missing.
Valid point, I think, but not critical in this case, since the patch
only affected gitrepository-layout(5) and gitglossary(7).
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?
Markus
next prev parent reply other threads:[~2008-12-17 19:56 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 [this message]
2008-12-17 21:29 ` [PATCH] githooks documentation: add a note about the +x mode Miklos Vajna
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=200812172055.45905.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=vmiklos@frugalware.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.