From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Jean-Noël AVILA" <jn.avila@free.fr>,
git@vger.kernel.org, "Adrian Ratiu" <adrian.ratiu@collabora.com>
Subject: Re: [PATCH 0/4] doc: hook: small improvements
Date: Sun, 24 May 2026 17:40:23 +0900 [thread overview]
Message-ID: <xmqqy0h9i4js.fsf@gitster.g> (raw)
In-Reply-To: <6cea9d6c-e72e-4b71-9380-41bcae72fd79@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sat, 23 May 2026 13:43:30 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Sat, May 23, 2026, at 12:24, Jean-Noël AVILA wrote:
>> On Thursday, 21 May 2026 18:25:54 CEST kristofferhaugsbakk@fastmail.com wrote:
>>> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>>>
>>> Topic name: kh/doc-hook
>>>
>>> Topic summary: Small improvements to git-hook(1) and the associated config.
>>>
>>> [1/4] doc: hook: remove stray backtick
>>> [2/4] doc: hook: consistently capitalize Git
>>> [3/4] doc: config: include existing git-hook(1) section
>>> [4/4] doc: hook: don’t self-link via config include
>>>
>>> Documentation/config.adoc | 2 ++
>>> Documentation/config/hook.adoc | 19 +++++++++++++------
>>> Documentation/git-hook.adoc | 11 ++++++-----
>>> 3 files changed, 21 insertions(+), 11 deletions(-)
>>>
>>>
>>> base-commit: aec3f587505a472db67e9462d0702e7d463a449d
>>
>> This series looks good to me.
>
> Thanks. Can I add your ack to the patches?
Sounds good. Typically we only honor an explicit Reviewed-by:, but
we add Acked-by: a lot more casually. "Looks good to me" you are
responding is typically good enough.
I'll mark the topic for 'next' in the draft edition of "What's
cooking" I work off of.
Thanks, both.
next prev parent reply other threads:[~2026-05-24 8:40 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 ` [PATCH 1/4] doc: hook: remove stray backtick kristofferhaugsbakk
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 [this message]
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=xmqqy0h9i4js.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adrian.ratiu@collabora.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=kristofferhaugsbakk@fastmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox