From: Junio C Hamano <gitster@pobox.com>
To: "Knut Harald Ryager via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Knut Harald Ryager" <e-k-nut@hotmail.com>,
"Josh Steadmon" <steadmon@google.com>,
"Jean-Noël Avila" <jn.avila@free.fr>
Subject: Re: [PATCH] docs: remove stray bracket from git-clone synopsis
Date: Thu, 31 Jul 2025 12:07:13 -0700 [thread overview]
Message-ID: <xmqqh5ysqivy.fsf@gitster.g> (raw)
In-Reply-To: <pull.2023.git.git.1753973177262.gitgitgadget@gmail.com> (Knut Harald Ryager via GitGitGadget's message of "Thu, 31 Jul 2025 14:46:17 +0000")
"Knut Harald Ryager via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> From: E-K-n <e-k-nut@hotmail.com>
This should be updated to match the name you use on your sign-off
below.
> The git-clone documentation contained an extra ‘]’ after
> `--also-filter-submodules]`.
It is correct to point out that the brackets are not matching, but I
think the one that you are removing a wrong one.
When f05da2b4 (clone, submodule: pass partial clone filters to
submodules, 2022-02-04) added an option --also-filter-submodules to
the command, it wanted to express that the option is only valid when
the "--filter=<filter-spec>" option is also given. And it did its
update correctly:
- [--filter=<filter>] [--] <repository>
+ [--filter=<filter> [--also-filter-submodules]] [--] <repository>
Later, 76880f05 (doc: git-clone: apply new documentation formatting
guidelines, 2024-03-29) introduced the extra closing bracket after
"--filter=<filter>" to make these two look as if they are unrelated
and independent, i.e.
[--filter=<filter>] [--also-filter-submodules]]
So, I think the one immediately after "--filter=<filter>" is what
you want to remove, not the one after "--also-filter-submodules".
> This patch removes the duplicate ‘]’ so that the line reads:
>
> [--also-filter-submodules] [--] <repository>
>
> instead of:
>
> [--also-filter-submodules]] [--] <repository>
We do not say "this patch does X" in our proposed log message.
Instead, you tell somebody sitting on the keyboard to "Do X".
IOW, something like
Remove the extra and incorrect closing bracket, so that the line
reads:
[--filter=<filter> [--also-filter-submodules]]
instead of
[--filter=<filter>] [--also-filter-submodules]]
is how we write this.
> Signed-off-by: Knut Harald Ryager <e-k-nut@hotmail.com>
> ---
> Remove excess right bracket from git-clone docs
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2023%2FKnutRyager%2Fmaster-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2023/KnutRyager/master-v1
> Pull-Request: https://github.com/git/git/pull/2023
>
> Documentation/git-clone.adoc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-clone.adoc b/Documentation/git-clone.adoc
> index 222d558290e..851502552f2 100644
> --- a/Documentation/git-clone.adoc
> +++ b/Documentation/git-clone.adoc
> @@ -16,7 +16,7 @@ git clone [--template=<template-directory>]
> [--depth <depth>] [--[no-]single-branch] [--[no-]tags]
> [--recurse-submodules[=<pathspec>]] [--[no-]shallow-submodules]
> [--[no-]remote-submodules] [--jobs <n>] [--sparse] [--[no-]reject-shallow]
> - [--filter=<filter-spec>] [--also-filter-submodules]] [--] <repository>
> + [--filter=<filter-spec>] [--also-filter-submodules] [--] <repository>
> [<directory>]
>
> DESCRIPTION
>
> base-commit: e813a0200a7121b97fec535f0d0b460b0a33356c
next prev parent reply other threads:[~2025-07-31 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 14:46 [PATCH] docs: remove stray bracket from git-clone synopsis Knut Harald Ryager via GitGitGadget
2025-07-31 19:07 ` Junio C Hamano [this message]
2025-08-10 21:30 ` [PATCH v2] Remove the extra and incorrect closing bracket, so that the line reads: Knut Harald Ryager via GitGitGadget
2025-08-11 6:14 ` Kristoffer Haugsbakk
2025-08-11 16:07 ` Junio C Hamano
2025-08-11 22:04 ` [PATCH v3] docs: remove stray bracket from git-clone synopsis Knut Harald Ryager via GitGitGadget
2025-08-12 15:55 ` 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=xmqqh5ysqivy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=e-k-nut@hotmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jn.avila@free.fr \
--cc=steadmon@google.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;
as well as URLs for NNTP newsgroup(s).