From: "starlord via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>, starlord <bojun.cbj@gmail.com>,
"bojun.cbj" <bojun.cbj@alibaba-inc.com>
Subject: [PATCH] doc: sparse-checkout: fix mismatched sq
Date: Thu, 21 May 2020 06:06:04 +0000 [thread overview]
Message-ID: <pull.641.git.1590041164665.gitgitgadget@gmail.com> (raw)
From: "bojun.cbj" <bojun.cbj@alibaba-inc.com>
Signed-off-by: bojun.cbj <bojun.cbj@alibaba-inc.com>
---
doc: sparse-checkout: fix mismatched sq
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-641%2FBerger7%2Fmaster-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-641/Berger7/master-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/641
Documentation/git-sparse-checkout.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-sparse-checkout.txt b/Documentation/git-sparse-checkout.txt
index 1a3ace60820..7c8943af7af 100644
--- a/Documentation/git-sparse-checkout.txt
+++ b/Documentation/git-sparse-checkout.txt
@@ -70,7 +70,7 @@ C-style quoted strings.
`core.sparseCheckoutCone` is enabled, the given patterns are interpreted
as directory names as in the 'set' subcommand.
-'reapply::
+'reapply'::
Reapply the sparsity pattern rules to paths in the working tree.
Commands like merge or rebase can materialize paths to do their
work (e.g. in order to show you a conflict), and other
base-commit: 87680d32efb6d14f162e54ad3bda4e3d6c908559
--
gitgitgadget
next reply other threads:[~2020-05-21 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 6:06 starlord via GitGitGadget [this message]
2020-05-21 6:14 ` [PATCH] doc: sparse-checkout: fix mismatched sq Elijah Newren
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=pull.641.git.1590041164665.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=bojun.cbj@alibaba-inc.com \
--cc=bojun.cbj@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@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).