From: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
To: gitster@pobox.com
Cc: derrickstolee@github.com, git@vger.kernel.org, vdye@github.com,
Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
Subject: [PATCH v5 4/4] Documentation/git-sparse-checkout.txt: some reword and modifications
Date: Sat, 19 Mar 2022 14:19:10 +0800 [thread overview]
Message-ID: <20220319061910.786850-5-shaoxuan.yuan02@gmail.com> (raw)
In-Reply-To: <20220319061910.786850-1-shaoxuan.yuan02@gmail.com>
Modifications suggested by Junio [1]
* remove redundant part under 'add' command
* fix broken indentation
* remove redundant part under '--[no-]cone' option
[1] https://lore.kernel.org/git/xmqqfsnfb42c.fsf@gitster.g/
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
---
Documentation/git-sparse-checkout.txt | 12 +++---------
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/Documentation/git-sparse-checkout.txt b/Documentation/git-sparse-checkout.txt
index 0178d63f56..482ecfe28c 100644
--- a/Documentation/git-sparse-checkout.txt
+++ b/Documentation/git-sparse-checkout.txt
@@ -66,11 +66,9 @@ file. See linkgit:git-worktree[1] and the documentation of
'add'::
Update the sparse-checkout file to include additional directories
- (in cone mode) or patterns (in non-cone mode). By default, these
- directories or patterns are read from the command-line arguments.
- These directories or patterns are interpreted the same way as stated
- above in `set` command, and they can be read from stdin using the
- `--stdin` option.
+ (in cone mode) or patterns (in non-cone mode). By default, these
+ directories or patterns are read from the command-line arguments,
+ but they can be read from stdin using the `--stdin` option.
'reapply'::
Reapply the sparsity pattern rules to paths in the working tree.
@@ -112,10 +110,6 @@ OPTIONS
'--[no-]cone'::
Use with the `set` and `reapply` commands.
Specify using cone mode or not. The default is to use cone mode.
-+
-For the `set` command, the option to use cone mode or not changes
-the interpretation of the remaining arguments to either be a list
-of directories or a list of patterns.
'--[no-]sparse-index'::
Use with the `set` and `reapply` commands.
--
2.35.1
next prev parent reply other threads:[~2022-03-19 6:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 13:21 [RFC PATCH 0/1] Documentation/git-sparse-checkout.txt: add an OPTIONS section Shaoxuan Yuan
2022-03-11 13:21 ` [RFC PATCH 1/1] " Shaoxuan Yuan
2022-03-11 20:56 ` Derrick Stolee
2022-03-14 6:34 ` [PATCH v2 0/1] " Shaoxuan Yuan
2022-03-14 6:34 ` [PATCH v2 1/1] " Shaoxuan Yuan
2022-03-14 6:56 ` [PATCH v3 0/1] " Shaoxuan Yuan
2022-03-14 6:56 ` [PATCH v3 1/1] " Shaoxuan Yuan
2022-03-14 16:13 ` Derrick Stolee
2022-03-17 12:37 ` [PATCH v4 0/1] " Shaoxuan Yuan
2022-03-17 12:37 ` [PATCH v4 1/1] " Shaoxuan Yuan
2022-03-18 16:47 ` Junio C Hamano
2022-03-18 16:30 ` [PATCH v4 0/1] " Junio C Hamano
2022-03-19 6:19 ` [PATCH v5 0/4] " Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 1/4] " Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 2/4] Documentation/git-sparse-checkout.txt: move OPTIONS after COMMANDS Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 3/4] Documentation/git-sparse-checkout.txt: some reword and modifications Shaoxuan Yuan
2022-03-19 6:19 ` Shaoxuan Yuan [this message]
2022-03-22 15:05 ` [PATCH v5 0/4] Documentation/git-sparse-checkout.txt: add an OPTIONS section Derrick Stolee
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=20220319061910.786850-5-shaoxuan.yuan02@gmail.com \
--to=shaoxuan.yuan02@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vdye@github.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).