All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>,
	Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, james@jamesliu.io,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	Phillip Wood <phillip.wood123@gmail.com>,
	"D. Ben Knoble" <ben.knoble@gmail.com>
Subject: Re: [PATCH v2] docs: document core.hooksPath=/dev/null
Date: Wed, 16 Apr 2025 20:25:28 -0400	[thread overview]
Message-ID: <9e14443c-e549-46e1-9fbf-ee72800e6944@gmail.com> (raw)
In-Reply-To: <BD8FCCB1-C97D-4057-982E-93A7F8B01AB9@gmail.com>

On 4/16/2025 12:53 PM, Lucas Seiki Oshiro wrote:
> Hi!
> 
>> +You can also disable all hooks entirely by setting `core.hooksPath`
>> +to `/dev/null`.
> 
> Personally I think it would be better to focus on the non-expert user,

I absolutely want this to be targeted for expert users, so users self-
select themselves into the risk of what happens when disabling hooks.
This is a "there be dragons here" kind of warning, implying that you
better know what you're doing if you are messing with hook paths.

Thanks,
-Stolee


  reply	other threads:[~2025-04-17  0:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 22:38 [PATCH] git: add --no-hooks global option Derrick Stolee via GitGitGadget
2025-04-03 22:55 ` brian m. carlson
2025-04-04  0:40   ` Derrick Stolee
2025-04-04 14:15 ` Phillip Wood
2025-04-14 10:59   ` Derrick Stolee
2025-04-16 10:29     ` Phillip Wood
2025-04-16 14:28       ` Junio C Hamano
2025-04-16 15:30         ` Derrick Stolee
2025-04-14 15:25   ` Lucas Seiki Oshiro
2025-04-14 21:05     ` brian m. carlson
2025-04-11 18:53 ` D. Ben Knoble
2025-04-16 15:42 ` [PATCH v2] docs: document core.hooksPath=/dev/null Derrick Stolee via GitGitGadget
2025-04-16 16:53   ` Lucas Seiki Oshiro
2025-04-17  0:25     ` Derrick Stolee [this message]
2025-04-17  0:39       ` brian m. carlson
2025-04-17  3:42         ` Junio C Hamano
2025-04-17 16:02       ` Lucas Seiki Oshiro

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=9e14443c-e549-46e1-9fbf-ee72800e6944@gmail.com \
    --to=stolee@gmail.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=james@jamesliu.io \
    --cc=lucasseikioshiro@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    /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.