Documentation: clarify/correct a few sparsity related statements
Reviewed-by: Derrick Stolee <dstolee@microsoft.com> Reviewed-by: Victoria Dye <vdye@github.com> Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Elijah Newren committed
Dec 14, 2021 at 04:09 UTC
d30e2bbe85d8a7427d5c978264f45d498a472408
2 files changed
+5
-5
Documentation/git-clone.txt
+4
-4
@@ -167,10 +167,10 @@ objects from the source repository into a pack in the cloned repository.
167
configuration variables are created.
168
169
--sparse::
170
- Initialize the sparse-checkout file so the working
171
- directory starts with only the files in the root
172
- of the repository. The sparse-checkout file can be
173
- modified to grow the working directory as needed.
170
+ Employ a sparse-checkout, with only files in the toplevel
171
+ directory initially being present. The
172
+ linkgit:git-sparse-checkout[1] command can be used to grow the
173
+ working directory as needed.
174
175
--filter=<filter-spec>::
176
Use the partial clone feature and request that the server sends
Documentation/git-sparse-checkout.txt
+1
-1
@@ -121,7 +121,7 @@ SPARSE CHECKOUT
121
It uses the skip-worktree bit (see linkgit:git-update-index[1]) to tell
122
Git whether a file in the working directory is worth looking at. If
123
the skip-worktree bit is set, then the file is ignored in the working
124
-directory. Git will not populate the contents of those files, which
124
+directory. Git will avoid populating the contents of those files, which
125
makes a sparse checkout helpful when working in a repository with many
126
files, but only a few are important to the current user.
127