From: Elijah Newren <newren@gmail.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] config/core.txt: fix minor issues for `core.sparseCheckoutCone`
Date: Mon, 18 Jul 2022 08:28:11 -0700 [thread overview]
Message-ID: <CABPp-BFGPbNNpoYRUogxQP7YvbEKJXyHcS13DEpG-tTr8RCzhA@mail.gmail.com> (raw)
In-Reply-To: <20220718100530.2068354-1-martin.agren@gmail.com>
On Mon, Jul 18, 2022 at 3:05 AM Martin Ågren <martin.agren@gmail.com> wrote:
>
> The sparse checkout feature can be used in "cone mode" or "non-cone
> mode". In this one instance in the documentation, we refer to the latter
> as "non cone mode" with whitespace rather than a hyphen. Align this with
> the rest of our documentation.
>
> A few words later in the same paragraph, there's mention of "a more
> flexible patterns". Drop that leading "a" to fix the grammar.
Ooh, sounds like a good catch.
> Signed-off-by: Martin Ågren <martin.agren@gmail.com>
> ---
> BTW, Elijah, it seems like you've recently started using different
> e-mail addresses, even within the same series [1]. Not sure if that's
> intentional or not? I decided to cc the one you've used by far the most
> rather than spamming all of your accounts.
Not intentional. Looks like it has already merged to next, though, or
I'd reroll and correct. Maybe I should submit an entry for .mailmap.
(Hard drive in my work computer died somewhat recently. There, I use
my work email for most things; almost everything other than git.git.
When recloning git.git on my replacement computer, I forgot to set
user.email in my git.git clone to override the value found in the
global ~/.gitconfig.)
> [1] https://lore.kernel.org/git/pull.1268.v4.git.1656984823.gitgitgadget@gmail.com/
>
> Documentation/config/core.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/config/core.txt b/Documentation/config/core.txt
> index 3ea3124f7f..37afbaf5a4 100644
> --- a/Documentation/config/core.txt
> +++ b/Documentation/config/core.txt
> @@ -722,8 +722,8 @@ core.sparseCheckout::
> core.sparseCheckoutCone::
> Enables the "cone mode" of the sparse checkout feature. When the
> sparse-checkout file contains a limited set of patterns, this
> - mode provides significant performance advantages. The "non
> - cone mode" can be requested to allow specifying a more flexible
> + mode provides significant performance advantages. The "non-cone
> + mode" can be requested to allow specifying more flexible
> patterns by setting this variable to 'false'. See
> linkgit:git-sparse-checkout[1] for more information.
>
> --
> 2.37.1.373.g4dd4a117ec
This looks good, thanks.
Reviewed-by: Elijah Newren <newren@gmail.com>
prev parent reply other threads:[~2022-07-18 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 10:05 [PATCH] config/core.txt: fix minor issues for `core.sparseCheckoutCone` Martin Ågren
2022-07-18 12:20 ` Derrick Stolee
2022-07-18 15:28 ` Elijah Newren [this message]
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=CABPp-BFGPbNNpoYRUogxQP7YvbEKJXyHcS13DEpG-tTr8RCzhA@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.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).