From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
jn.avila@free.fr, adrian.ratiu@collabora.com
Subject: [PATCH 1/4] doc: hook: remove stray backtick
Date: Thu, 21 May 2026 18:25:55 +0200 [thread overview]
Message-ID: <doc_hook_stray_backtick.6f1@msgid.xyz> (raw)
In-Reply-To: <CV_doc_hook.6f0@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Documentation/git-hook.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-hook.adoc b/Documentation/git-hook.adoc
index 46ea52db55f..96c5c9c3c23 100644
--- a/Documentation/git-hook.adoc
+++ b/Documentation/git-hook.adoc
@@ -41,7 +41,7 @@ spell-checker for your commit messages, you would write a configuration like so:
With this config, when you run 'git commit', first `~/bin/linter --cpp20` will
have a chance to check your files to be committed (during the `pre-commit` hook
-event`), and then `~/bin/spellchecker` will have a chance to check your commit
+event), and then `~/bin/spellchecker` will have a chance to check your commit
message (during the `commit-msg` hook event).
Commands are run in the order Git encounters their associated
--
2.54.0.13.g9c7419e39f8
next prev parent reply other threads:[~2026-05-21 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 16:25 [PATCH 0/4] doc: hook: small improvements kristofferhaugsbakk
2026-05-21 16:25 ` kristofferhaugsbakk [this message]
2026-05-21 16:25 ` [PATCH 2/4] doc: hook: consistently capitalize Git kristofferhaugsbakk
2026-05-21 16:25 ` [PATCH 3/4] doc: config: include existing git-hook(1) section kristofferhaugsbakk
2026-05-21 16:25 ` [PATCH 4/4] doc: hook: don’t self-link via config include kristofferhaugsbakk
2026-05-23 10:24 ` [PATCH 0/4] doc: hook: small improvements Jean-Noël AVILA
2026-05-23 11:43 ` Kristoffer Haugsbakk
2026-05-24 8:40 ` Junio C Hamano
2026-05-25 10:58 ` Adrian Ratiu
2026-05-25 11:09 ` Junio C Hamano
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=doc_hook_stray_backtick.6f1@msgid.xyz \
--to=kristofferhaugsbakk@fastmail.com \
--cc=adrian.ratiu@collabora.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
/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.