Re: Configuring a third-party git hook
- From
Chris Angelico <rosuav@gmail.com>
- Date
- Mar 20, 2014, 16:51 UTC
- Message-ID
- <CAPTjJmpAcmVGgJK8iUvFuXJq_ZukisRZ6OD9TM=feuxDYm5iPQ@mail.gmail.com>
- In-Reply-To
- <CAO54GHC1B6hj-OvibHn2=-B25Xd5EmfWsphJ1S7vE4bgUUX3Bw@mail.gmail.com>
On Thu, Mar 20, 2014 at 11:53 PM, Kevin <ikke@ikke.info> wrote:
Show 9 quoted lines
> On Wed, Mar 19, 2014 at 12:16 PM, Chris Angelico <rosuav@gmail.com> wrote: >> Two parts to the question, then. Firstly, is it acceptable to use 'git >> config' for a hook like this? And secondly, either: Is there a naming >> convention to follow? or, what alternative would you recommend? > > 1. I would say yes. git config is made to be extended and doesn't > require a config item to be known. > 2. Namespacing the config items like you did is a good thing to do so > it won't interfere with other options.
Excellent! Thank you.
Is this documented anywhere? The git config man page says to look to other git man pages:
https://www.kernel.org/pub/software/scm/git/docs/git-config.html#_variables
A comment there to the effect that "Third party tools may also define their own variables" or something would make it clear that this is the intention.
ChrisA