From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Josh Soref" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Jean-Noël AVILA" <jn.avila@free.fr>
Subject: Re: [PATCH v2 2/2] doc: correct minor wording issues
Date: Mon, 22 Dec 2025 13:42:38 +0900 [thread overview]
Message-ID: <xmqqms3brutd.fsf@gitster.g> (raw)
In-Reply-To: <80146290-bbe3-4da4-b951-04399bc2fd03@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sun, 21 Dec 2025 18:13:18 +0100")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Fri, Dec 19, 2025, at 19:54, Jean-Noël Avila via GitGitGadget wrote:
>> From: =?UTF-8?q?Jean-No=C3=ABl=20Avila?= <jn.avila@free.fr>
>>
>> * use imperative mood for consistency in options descriptions
>> * add missing parenthesis
>> * reword verbose phrase in git-repack.adoc
>>
>> Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
>
> I have reviewed these changes in v1 since the changes are the same but
> split into two commits instead of one.
>
> Acked-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Thanks for reviewing.
I've also reviewed the v2 hours ago and the patches are now already
in 'next'.
next prev parent reply other threads:[~2025-12-22 4:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 20:23 [PATCH] doc: flock of small fixes to various documentation files Jean-Noël Avila via GitGitGadget
2025-12-15 22:50 ` Kristoffer Haugsbakk
2025-12-17 13:45 ` Jean-Noël Avila
2025-12-18 8:05 ` Kristoffer Haugsbakk
2025-12-19 9:34 ` Kristoffer Haugsbakk
2025-12-19 18:54 ` [PATCH v2 0/2] " Jean-Noël Avila via GitGitGadget
2025-12-19 18:54 ` [PATCH v2 1/2] doc: fix asciidoc markup issues in several files Jean-Noël Avila via GitGitGadget
2025-12-21 17:13 ` Kristoffer Haugsbakk
2025-12-19 18:54 ` [PATCH v2 2/2] doc: correct minor wording issues Jean-Noël Avila via GitGitGadget
2025-12-21 17:13 ` Kristoffer Haugsbakk
2025-12-22 4:42 ` Junio C Hamano [this message]
2025-12-21 17:12 ` [PATCH v2 0/2] doc: flock of small fixes to various documentation files Kristoffer Haugsbakk
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=xmqqms3brutd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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 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.