diff options
Diffstat (limited to 'man1/git-sparse-checkout.1')
| -rw-r--r-- | man1/git-sparse-checkout.1 | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/man1/git-sparse-checkout.1 b/man1/git-sparse-checkout.1 index 4a3c11a83..14d691d94 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: 03/21/2023 +.\" Date: 03/28/2023 .\" Manual: Git Manual -.\" Source: Git 2.40.0.130.g27d43aaaf5 +.\" Source: Git 2.40.0.141.g8d90352acc .\" Language: English .\" -.TH "GIT\-SPARSE\-CHECKOU" "1" "03/21/2023" "Git 2\&.40\&.0\&.130\&.g27d43a" "Git Manual" +.TH "GIT\-SPARSE\-CHECKOU" "1" "03/28/2023" "Git 2\&.40\&.0\&.141\&.g8d9035" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -288,7 +288,7 @@ It has edge cases where the "right" behavior is unclear\&. Two examples: .\} .nf First, two users are in a subdirectory, and the first runs - git sparse\-checkout set \(aq/toplevel\-dir/*\&.c\(aq + git sparse\-checkout set \*(Aq/toplevel\-dir/*\&.c\*(Aq while the second runs git sparse\-checkout set relative\-dir Should those arguments be transliterated into @@ -300,8 +300,8 @@ the first command is probably aware that arguments to set/add are supposed to be patterns in non\-cone mode, and probably would not be happy with such a transliteration\&. However, many gitignore\-style patterns are just paths, which might be what the user who typed the -second command was thinking, and they\(aqd be upset if their argument -wasn\(aqt transliterated\&. +second command was thinking, and they\*(Aqd be upset if their argument +wasn\*(Aqt transliterated\&. .fi .if n \{\ .RE @@ -314,11 +314,11 @@ wasn\(aqt transliterated\&. Second, what should bash\-completion complete on for set/add commands 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 +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 "/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, +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\&.) Completing on files or directories might give nasty surprises in all these cases\&. @@ -396,7 +396,7 @@ For example, to select everything, and then to remove the file \fBunwanted\fR (s .RS 4 .\} .nf -git sparse\-checkout set \-\-no\-cone \(aq/*\(aq \(aq!unwanted\(aq +git sparse\-checkout set \-\-no\-cone \*(Aq/*\*(Aq \*(Aq!unwanted\*(Aq .fi .if n \{\ .RE |