Jeff King writes:
> On Wed, Aug 20, 2014 at 08:55:52PM +1200, Chris Packham wrote:
>
>> I actually find the existing behaviour useful. If I want to disable a
>> hook to I can just chmod -x .git/hook/... and I then chmod +x it when
>> I want to re-enable it. I guess I could live with an extra warn
On Wed, Aug 20, 2014 at 08:55:52PM +1200, Chris Packham wrote:
> I actually find the existing behaviour useful. If I want to disable a
> hook to I can just chmod -x .git/hook/... and I then chmod +x it when
> I want to re-enable it. I guess I could live with an extra warning as
> long as the comma
On Wed, Aug 20, 2014 at 4:52 AM, Junio C Hamano wrote:
> Jeff King writes:
>
>> On Tue, Aug 19, 2014 at 04:05:21PM +1000, Babak M wrote:
>>
>>> I saw that if a hook file is present in .git/hooks and it does not
>>> have execution permissions it is silently ignored.
>>>
>>> I thought it might be w
Jeff King writes:
> On Tue, Aug 19, 2014 at 04:05:21PM +1000, Babak M wrote:
>
>> I saw that if a hook file is present in .git/hooks and it does not
>> have execution permissions it is silently ignored.
>>
>> I thought it might be worthwhile issuing a warning such as "Warning:
>> pre-commit hook
On Tue, Aug 19, 2014 at 04:05:21PM +1000, Babak M wrote:
> I saw that if a hook file is present in .git/hooks and it does not
> have execution permissions it is silently ignored.
>
> I thought it might be worthwhile issuing a warning such as "Warning:
> pre-commit hook exists but it cannot be exe
Hi,
I saw that if a hook file is present in .git/hooks and it does not
have execution permissions it is silently ignored.
I thought it might be worthwhile issuing a warning such as "Warning:
pre-commit hook exists but it cannot be executed due to insufficient
permissions".
Not sure if this has b
6 matches
Mail list logo
