summaryrefslogtreecommitdiffstats
path: root/man1/git-sparse-checkout.1
diff options
context:
space:
mode:
Diffstat (limited to 'man1/git-sparse-checkout.1')
-rw-r--r--man1/git-sparse-checkout.18
1 files changed, 4 insertions, 4 deletions
diff --git a/man1/git-sparse-checkout.1 b/man1/git-sparse-checkout.1
index 6f34dfa72..e2fc1ca0d 100644
--- a/man1/git-sparse-checkout.1
+++ b/man1/git-sparse-checkout.1
@@ -2,12 +2,12 @@
.\" Title: git-sparse-checkout
.\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\" Date: 2023-06-13
+.\" Date: 2023-06-23
.\" Manual: Git Manual
-.\" Source: Git 2.41.0.28.gd7d8841f67
+.\" Source: Git 2.41.0.191.g6ff334181c
.\" Language: English
.\"
-.TH "GIT\-SPARSE\-CHECKOUT" "1" "2023\-06\-13" "Git 2\&.41\&.0\&.28\&.gd7d8841" "Git Manual"
+.TH "GIT\-SPARSE\-CHECKOUT" "1" "2023\-06\-23" "Git 2\&.41\&.0\&.191\&.g6ff334" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -348,7 +348,7 @@ for non\-cone users? If it suggests paths, is it exacerbating the
problem above? Also, if it suggests paths, what if the user has a
file or directory that begins with either a \*(Aq!\*(Aq or \*(Aq#\*(Aq or has a \*(Aq*\*(Aq,
\*(Aq\e\*(Aq, \*(Aq?\*(Aq, \*(Aq[\*(Aq, or \*(Aq]\*(Aq in its name? And if it suggests paths, will
-it complete "/pro" to "/proc" (in the root filesytem) rather than to
+it complete "/pro" to "/proc" (in the root filesystem) rather than to
"/progress\&.txt" in the current directory? (Note that users are
likely to want to start paths with a leading \*(Aq/\*(Aq in non\-cone mode,
for the same reason that \&.gitignore files often have one\&.)