doc: fix inappropriate monospace formatting
Signed-off-by: Andreas Heiduk <asheiduk@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Andreas Heiduk committed
Oct 22, 2018 at 22:45 UTC
ad471949f46c774fcdada93f376360057c6ec777
5 files changed
+40
-32
Documentation/git-upload-pack.txt
+1
@@ -11,6 +11,7 @@ SYNOPSIS
11
[verse]
12
'git-upload-pack' [--[no-]strict] [--timeout=<n>] [--stateless-rpc]
13
[--advertise-refs] <directory>
14
+
15
DESCRIPTION
16
-----------
17
Invoked by 'git fetch-pack', learns what
Documentation/git.txt
+5
-5
@@ -402,11 +402,11 @@ Git so take care if using a foreign front-end.
402
of Git object directories which can be used to search for Git
403
objects. New objects will not be written to these directories.
404
+
405
- Entries that begin with `"` (double-quote) will be interpreted
406
- as C-style quoted paths, removing leading and trailing
407
- double-quotes and respecting backslash escapes. E.g., the value
408
- `"path-with-\"-and-:-in-it":vanilla-path` has two paths:
409
- `path-with-"-and-:-in-it` and `vanilla-path`.
405
+Entries that begin with `"` (double-quote) will be interpreted
406
+as C-style quoted paths, removing leading and trailing
407
+double-quotes and respecting backslash escapes. E.g., the value
408
+`"path-with-\"-and-:-in-it":vanilla-path` has two paths:
409
+`path-with-"-and-:-in-it` and `vanilla-path`.
410
411
`GIT_DIR`::
412
If the `GIT_DIR` environment variable is set then it
Documentation/gitattributes.txt
+15
-15
@@ -303,21 +303,21 @@ number of pitfalls:
303
attribute. If you decide to use the `working-tree-encoding` attribute
304
in your repository, then it is strongly recommended to ensure that all
305
clients working with the repository support it.
306
-
307
- For example, Microsoft Visual Studio resources files (`*.rc`) or
308
- PowerShell script files (`*.ps1`) are sometimes encoded in UTF-16.
309
- If you declare `*.ps1` as files as UTF-16 and you add `foo.ps1` with
310
- a `working-tree-encoding` enabled Git client, then `foo.ps1` will be
311
- stored as UTF-8 internally. A client without `working-tree-encoding`
312
- support will checkout `foo.ps1` as UTF-8 encoded file. This will
313
- typically cause trouble for the users of this file.
314
-
315
- If a Git client, that does not support the `working-tree-encoding`
316
- attribute, adds a new file `bar.ps1`, then `bar.ps1` will be
317
- stored "as-is" internally (in this example probably as UTF-16).
318
- A client with `working-tree-encoding` support will interpret the
319
- internal contents as UTF-8 and try to convert it to UTF-16 on checkout.
320
- That operation will fail and cause an error.
306
++
307
+For example, Microsoft Visual Studio resources files (`*.rc`) or
308
+PowerShell script files (`*.ps1`) are sometimes encoded in UTF-16.
309
+If you declare `*.ps1` as files as UTF-16 and you add `foo.ps1` with
310
+a `working-tree-encoding` enabled Git client, then `foo.ps1` will be
311
+stored as UTF-8 internally. A client without `working-tree-encoding`
312
+support will checkout `foo.ps1` as UTF-8 encoded file. This will
313
+typically cause trouble for the users of this file.
314
++
315
+If a Git client, that does not support the `working-tree-encoding`
316
+attribute, adds a new file `bar.ps1`, then `bar.ps1` will be
317
+stored "as-is" internally (in this example probably as UTF-16).
318
+A client with `working-tree-encoding` support will interpret the
319
+internal contents as UTF-8 and try to convert it to UTF-16 on checkout.
320
+That operation will fail and cause an error.
321
322
- Reencoding content to non-UTF encodings can cause errors as the
323
conversion might not be UTF-8 round trip safe. If you suspect your
Documentation/gitmodules.txt
+10
-7
@@ -67,7 +67,8 @@ submodule.<name>.fetchRecurseSubmodules::
67
submodule.<name>.ignore::
68
Defines under what circumstances "git status" and the diff family show
69
a submodule as modified. The following values are supported:
70
-
70
++
71
+--
72
all;; The submodule will never be considered modified (but will
73
nonetheless show up in the output of status and commit when it has
74
been staged).
@@ -84,12 +85,14 @@ submodule.<name>.ignore::
85
differences, and modifications to tracked and untracked files are
86
shown. This is the default option.
87
87
- If this option is also present in the submodules entry in .git/config
88
- of the superproject, the setting there will override the one found in
89
- .gitmodules.
90
- Both settings can be overridden on the command line by using the
91
- "--ignore-submodule" option. The 'git submodule' commands are not
92
- affected by this setting.
88
+If this option is also present in the submodules entry in .git/config
89
+of the superproject, the setting there will override the one found in
90
+.gitmodules.
91
+
92
+Both settings can be overridden on the command line by using the
93
+"--ignore-submodule" option. The 'git submodule' commands are not
94
+affected by this setting.
95
+--
96
97
submodule.<name>.shallow::
98
When set to true, a clone of this submodule will be performed as a
Documentation/gitsubmodules.txt
+9
-5
@@ -169,11 +169,15 @@ ACTIVE SUBMODULES
169
170
A submodule is considered active,
171
172
- (a) if `submodule.<name>.active` is set to `true`
173
- or
174
- (b) if the submodule's path matches the pathspec in `submodule.active`
175
- or
176
- (c) if `submodule.<name>.url` is set.
172
+ a. if `submodule.<name>.active` is set to `true`
173
++
174
+or
175
+
176
+ b. if the submodule's path matches the pathspec in `submodule.active`
177
++
178
+or
179
+
180
+ c. if `submodule.<name>.url` is set.
181
182
and these are evaluated in this order.
183