doc: change configuration variables format
This change configuration variables that where in italic style to monospace font according to the guideline. It was obtained with grep '[[:alpha:]]*\.[[:alpha:]]*::$' config.txt | \ sed -e 's/::$//' -e 's/\./\\\\./' | \ xargs -iP perl -pi -e "s/\'P\'/\`P\`/g" ./*.txt Signed-off-by: Tom Russello <tom.russello@grenoble-inp.org> Signed-off-by: Erwan Mathoniere <erwan.mathoniere@grenoble-inp.org> Signed-off-by: Samuel Groot <samuel.groot@grenoble-inp.org> Signed-off-by: Matthieu Moy <matthieu.moy@grenoble-inp.fr> Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Tom Russello committed
Jun 8, 2016 at 19:23 UTC
ae9f6311e9c15d7968c2d03eab6e929e9c9d5f42
17 files changed
+86
-86
Documentation/config.txt
+13
-13
@@ -545,7 +545,7 @@ core.compression::
545
-1 is the zlib default. 0 means no compression,
546
and 1..9 are various speed/size tradeoffs, 9 being slowest.
547
If set, this provides a default to other compression variables,
548
- such as 'core.looseCompression' and 'pack.compression'.
548
+ such as `core.looseCompression` and `pack.compression`.
549
550
core.looseCompression::
551
An integer -1..9, indicating the compression level for objects that
@@ -1400,18 +1400,18 @@ gitcvs.usecrlfattr::
1400
treat it as text. If they suppress text conversion, the file
1401
will be set with '-kb' mode, which suppresses any newline munging
1402
the client might otherwise do. If the attributes do not allow
1403
- the file type to be determined, then 'gitcvs.allBinary' is
1403
+ the file type to be determined, then `gitcvs.allBinary` is
1404
used. See linkgit:gitattributes[5].
1405
1406
gitcvs.allBinary::
1407
- This is used if 'gitcvs.usecrlfattr' does not resolve
1407
+ This is used if `gitcvs.usecrlfattr` does not resolve
1408
the correct '-kb' mode to use. If true, all
1409
unresolved files are sent to the client in
1410
mode '-kb'. This causes the client to treat them
1411
as binary files, which suppresses any newline munging it
1412
otherwise might do. Alternatively, if it is set to "guess",
1413
then the contents of the file are examined to decide if
1414
- it is binary, similar to 'core.autocrlf'.
1414
+ it is binary, similar to `core.autocrlf`.
1415
1416
gitcvs.dbName::
1417
Database used by git-cvsserver to cache revision information
@@ -1430,7 +1430,7 @@ gitcvs.dbDriver::
1430
See linkgit:git-cvsserver[1].
1431
1432
gitcvs.dbUser, gitcvs.dbPass::
1433
- Database user and password. Only useful if setting 'gitcvs.dbDriver',
1433
+ Database user and password. Only useful if setting `gitcvs.dbDriver`,
1434
since SQLite has no concept of database users and/or passwords.
1435
'gitcvs.dbUser' supports variable substitution (see
1436
linkgit:git-cvsserver[1] for details).
@@ -1442,8 +1442,8 @@ gitcvs.dbTableNamePrefix::
1442
linkgit:git-cvsserver[1] for details). Any non-alphabetic
1443
characters will be replaced with underscores.
1444
1445
-All gitcvs variables except for 'gitcvs.usecrlfattr' and
1446
-'gitcvs.allBinary' can also be specified as
1445
+All gitcvs variables except for `gitcvs.usecrlfattr` and
1446
+`gitcvs.allBinary` can also be specified as
1447
'gitcvs.<access_method>.<varname>' (where 'access_method'
1448
is one of "ext" and "pserver") to make them apply only for the given
1449
access method.
@@ -1476,7 +1476,7 @@ grep.patternType::
1476
1477
grep.extendedRegexp::
1478
If set to true, enable '--extended-regexp' option by default. This
1479
- option is ignored when the 'grep.patternType' option is set to a value
1479
+ option is ignored when the `grep.patternType` option is set to a value
1480
other than 'default'.
1481
1482
grep.threads::
@@ -2587,7 +2587,7 @@ sendemail.identity::
2587
A configuration identity. When given, causes values in the
2588
'sendemail.<identity>' subsection to take precedence over
2589
values in the 'sendemail' section. The default identity is
2590
- the value of 'sendemail.identity'.
2590
+ the value of `sendemail.identity`.
2591
2592
sendemail.smtpEncryption::
2593
See linkgit:git-send-email[1] for description. Note that this
@@ -2604,7 +2604,7 @@ sendemail.<identity>.*::
2604
Identity-specific versions of the 'sendemail.*' parameters
2605
found below, taking precedence over those when the this
2606
identity is selected, through command-line or
2607
- 'sendemail.identity'.
2607
+ `sendemail.identity`.
2608
2609
sendemail.aliasesFile::
2610
sendemail.aliasFileType::
@@ -2634,7 +2634,7 @@ sendemail.xmailer::
2634
See linkgit:git-send-email[1] for description.
2635
2636
sendemail.signedoffcc (deprecated)::
2637
- Deprecated alias for 'sendemail.signedoffbycc'.
2637
+ Deprecated alias for `sendemail.signedoffbycc`.
2638
2639
showbranch.default::
2640
The default set of branches for linkgit:git-show-branch[1].
@@ -2864,8 +2864,8 @@ user.name::
2864
environment variables. See linkgit:git-commit-tree[1].
2865
2866
user.useConfigOnly::
2867
- Instruct Git to avoid trying to guess defaults for 'user.email'
2868
- and 'user.name', and instead retrieve the values only from the
2867
+ Instruct Git to avoid trying to guess defaults for `user.email`
2868
+ and `user.name`, and instead retrieve the values only from the
2869
configuration. For example, if you have multiple email addresses
2870
and would like to use a different one for each repository, then
2871
with this configuration option set to `true` in the global config
Documentation/diff-config.txt
+1
-1
@@ -75,7 +75,7 @@ diff.ignoreSubmodules::
75
commands such as 'git diff-files'. 'git checkout' also honors
76
this setting when reporting uncommitted changes. Setting it to
77
'all' disables the submodule summary normally shown by 'git commit'
78
- and 'git status' when 'status.submoduleSummary' is set unless it is
78
+ and 'git status' when `status.submoduleSummary` is set unless it is
79
overridden by using the --ignore-submodules command-line option.
80
The 'git submodule' commands are not affected by this setting.
81
Documentation/git-commit.txt
+1
-1
@@ -201,7 +201,7 @@ default::
201
Otherwise `whitespace`.
202
--
203
+
204
-The default can be changed by the 'commit.cleanup' configuration
204
+The default can be changed by the `commit.cleanup` configuration
205
variable (see linkgit:git-config[1]).
206
207
-e::
Documentation/git-format-patch.txt
+3
-3
@@ -58,7 +58,7 @@ output, unless the `--stdout` option is specified.
58
59
If `-o` is specified, output files are created in <dir>. Otherwise
60
they are created in the current working directory. The default path
61
-can be set with the 'format.outputDirectory' configuration option.
61
+can be set with the `format.outputDirectory` configuration option.
62
The `-o` option takes precedence over `format.outputDirectory`.
63
To store patches in the current working directory even when
64
`format.outputDirectory` points elsewhere, use `-o .`.
@@ -146,9 +146,9 @@ series, where the head is chosen from the cover letter, the
146
`--in-reply-to`, and the first patch mail, in this order. 'deep'
147
threading makes every mail a reply to the previous one.
148
+
149
-The default is `--no-thread`, unless the 'format.thread' configuration
149
+The default is `--no-thread`, unless the `format.thread` configuration
150
is set. If `--thread` is specified without a style, it defaults to the
151
-style specified by 'format.thread' if any, or else `shallow`.
151
+style specified by `format.thread` if any, or else `shallow`.
152
+
153
Beware that the default for 'git send-email' is to thread emails
154
itself. If you want `git format-patch` to take care of threading, you
Documentation/git-gc.txt
+8
-8
@@ -82,13 +82,13 @@ automatic consolidation of packs.
82
Configuration
83
-------------
84
85
-The optional configuration variable 'gc.reflogExpire' can be
85
+The optional configuration variable `gc.reflogExpire` can be
86
set to indicate how long historical entries within each branch's
87
reflog should remain available in this repository. The setting is
88
expressed as a length of time, for example '90 days' or '3 months'.
89
It defaults to '90 days'.
90
91
-The optional configuration variable 'gc.reflogExpireUnreachable'
91
+The optional configuration variable `gc.reflogExpireUnreachable`
92
can be set to indicate how long historical reflog entries which
93
are not part of the current branch should remain available in
94
this repository. These types of entries are generally created as
@@ -107,30 +107,30 @@ branches:
107
reflogExpireUnreachable = 3 days
108
------------
109
110
-The optional configuration variable 'gc.rerereResolved' indicates
110
+The optional configuration variable `gc.rerereResolved` indicates
111
how long records of conflicted merge you resolved earlier are
112
kept. This defaults to 60 days.
113
114
-The optional configuration variable 'gc.rerereUnresolved' indicates
114
+The optional configuration variable `gc.rerereUnresolved` indicates
115
how long records of conflicted merge you have not resolved are
116
kept. This defaults to 15 days.
117
118
-The optional configuration variable 'gc.packRefs' determines if
118
+The optional configuration variable `gc.packRefs` determines if
119
'git gc' runs 'git pack-refs'. This can be set to "notbare" to enable
120
it within all non-bare repos or it can be set to a boolean value.
121
This defaults to true.
122
123
-The optional configuration variable 'gc.aggressiveWindow' controls how
123
+The optional configuration variable `gc.aggressiveWindow` controls how
124
much time is spent optimizing the delta compression of the objects in
125
the repository when the --aggressive option is specified. The larger
126
the value, the more time is spent optimizing the delta compression. See
127
the documentation for the --window' option in linkgit:git-repack[1] for
128
more details. This defaults to 250.
129
130
-Similarly, the optional configuration variable 'gc.aggressiveDepth'
130
+Similarly, the optional configuration variable `gc.aggressiveDepth`
131
controls --depth option in linkgit:git-repack[1]. This defaults to 250.
132
133
-The optional configuration variable 'gc.pruneExpire' controls how old
133
+The optional configuration variable `gc.pruneExpire` controls how old
134
the unreferenced loose objects have to be before they are pruned. The
135
default is "2 weeks ago".
136
Documentation/git-grep.txt
+1
-1
@@ -51,7 +51,7 @@ grep.patternType::
51
52
grep.extendedRegexp::
53
If set to true, enable '--extended-regexp' option by default. This
54
- option is ignored when the 'grep.patternType' option is set to a value
54
+ option is ignored when the `grep.patternType` option is set to a value
55
other than 'default'.
56
57
grep.threads::
Documentation/git-help.txt
+12
-12
@@ -57,10 +57,10 @@ OPTIONS
57
--man::
58
Display manual page for the command in the 'man' format. This
59
option may be used to override a value set in the
60
- 'help.format' configuration variable.
60
+ `help.format` configuration variable.
61
+
62
By default the 'man' program will be used to display the manual page,
63
-but the 'man.viewer' configuration variable may be used to choose
63
+but the `man.viewer` configuration variable may be used to choose
64
other display programs (see below).
65
66
-w::
@@ -69,7 +69,7 @@ other display programs (see below).
69
format. A web browser will be used for that purpose.
70
+
71
The web browser can be specified using the configuration variable
72
-'help.browser', or 'web.browser' if the former is not set. If none of
72
+`help.browser`, or `web.browser` if the former is not set. If none of
73
these config variables is set, the 'git web{litdd}browse' helper script
74
(called by 'git help') will pick a suitable default. See
75
linkgit:git-web{litdd}browse[1] for more information about this.
@@ -80,7 +80,7 @@ CONFIGURATION VARIABLES
80
help.format
81
~~~~~~~~~~~
82
83
-If no command-line option is passed, the 'help.format' configuration
83
+If no command-line option is passed, the `help.format` configuration
84
variable will be checked. The following values are supported for this
85
variable; they make 'git help' behave as their corresponding command-
86
line option:
@@ -92,7 +92,7 @@ line option:
92
help.browser, web.browser and browser.<tool>.path
93
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
94
95
-The 'help.browser', 'web.browser' and 'browser.<tool>.path' will also
95
+The `help.browser`, `web.browser` and `browser.<tool>.path` will also
96
be checked if the 'web' format is chosen (either by command-line
97
option or configuration variable). See '-w|--web' in the OPTIONS
98
section above and linkgit:git-web{litdd}browse[1].
@@ -100,7 +100,7 @@ section above and linkgit:git-web{litdd}browse[1].
100
man.viewer
101
~~~~~~~~~~
102
103
-The 'man.viewer' configuration variable will be checked if the 'man'
103
+The `man.viewer` configuration variable will be checked if the 'man'
104
format is chosen. The following values are currently supported:
105
106
* "man": use the 'man' program as usual,
@@ -110,9 +110,9 @@ format is chosen. The following values are currently supported:
110
tab (see 'Note about konqueror' below).
111
112
Values for other tools can be used if there is a corresponding
113
-'man.<tool>.cmd' configuration entry (see below).
113
+`man.<tool>.cmd` configuration entry (see below).
114
115
-Multiple values may be given to the 'man.viewer' configuration
115
+Multiple values may be given to the `man.viewer` configuration
116
variable. Their corresponding programs will be tried in the order
117
listed in the configuration file.
118
@@ -135,7 +135,7 @@ man.<tool>.path
135
~~~~~~~~~~~~~~~
136
137
You can explicitly provide a full path to your preferred man viewer by
138
-setting the configuration variable 'man.<tool>.path'. For example, you
138
+setting the configuration variable `man.<tool>.path`. For example, you
139
can configure the absolute path to konqueror by setting
140
'man.konqueror.path'. Otherwise, 'git help' assumes the tool is
141
available in PATH.
@@ -143,9 +143,9 @@ available in PATH.
143
man.<tool>.cmd
144
~~~~~~~~~~~~~~
145
146
-When the man viewer, specified by the 'man.viewer' configuration
146
+When the man viewer, specified by the `man.viewer` configuration
147
variables, is not among the supported ones, then the corresponding
148
-'man.<tool>.cmd' configuration variable will be looked up. If this
148
+`man.<tool>.cmd` configuration variable will be looked up. If this
149
variable exists then the specified tool will be treated as a custom
150
command and a shell eval will be used to run the command with the man
151
page passed as arguments.
@@ -153,7 +153,7 @@ page passed as arguments.
153
Note about konqueror
154
~~~~~~~~~~~~~~~~~~~~
155
156
-When 'konqueror' is specified in the 'man.viewer' configuration
156
+When 'konqueror' is specified in the `man.viewer` configuration
157
variable, we launch 'kfmclient' to try to open the man page on an
158
already opened konqueror in a new tab if possible.
159
Documentation/git-instaweb.txt
+2
-2
@@ -80,8 +80,8 @@ You may specify configuration in your .git/config
80
81
-----------------------------------------------------------------------
82
83
-If the configuration variable 'instaweb.browser' is not set,
84
-'web.browser' will be used instead if it is defined. See
83
+If the configuration variable `instaweb.browser` is not set,
84
+`web.browser` will be used instead if it is defined. See
85
linkgit:git-web{litdd}browse[1] for more information about this.
86
87
SEE ALSO
Documentation/git-push.txt
+3
-3
@@ -137,8 +137,8 @@ already exists on the remote side.
137
and also push annotated tags in `refs/tags` that are missing
138
from the remote but are pointing at commit-ish that are
139
reachable from the refs being pushed. This can also be specified
140
- with configuration variable 'push.followTags'. For more
141
- information, see 'push.followTags' in linkgit:git-config[1].
140
+ with configuration variable `push.followTags`. For more
141
+ information, see `push.followTags` in linkgit:git-config[1].
142
143
--[no-]signed::
144
--sign=(true|false|if-asked)::
@@ -240,7 +240,7 @@ origin +master` to force a push to the `master` branch). See the
240
For every branch that is up to date or successfully pushed, add
241
upstream (tracking) reference, used by argument-less
242
linkgit:git-pull[1] and other commands. For more information,
243
- see 'branch.<name>.merge' in linkgit:git-config[1].
243
+ see `branch.<name>.merge` in linkgit:git-config[1].
244
245
--[no-]thin::
246
These options are passed to linkgit:git-send-pack[1]. A thin transfer
Documentation/git-send-email.txt
+31
-31
@@ -47,18 +47,18 @@ Composing
47
48
--annotate::
49
Review and edit each patch you're about to send. Default is the value
50
- of 'sendemail.annotate'. See the CONFIGURATION section for
51
- 'sendemail.multiEdit'.
50
+ of `sendemail.annotate`. See the CONFIGURATION section for
51
+ `sendemail.multiEdit`.
52
53
--bcc=<address>,...::
54
Specify a "Bcc:" value for each email. Default is the value of
55
- 'sendemail.bcc'.
55
+ `sendemail.bcc`.
56
+
57
This option may be specified multiple times.
58
59
--cc=<address>,...::
60
Specify a starting "Cc:" value for each email.
61
- Default is the value of 'sendemail.cc'.
61
+ Default is the value of `sendemail.cc`.
62
+
63
This option may be specified multiple times.
64
@@ -74,12 +74,12 @@ and In-Reply-To headers will be used unless they are removed.
74
+
75
Missing From or In-Reply-To headers will be prompted for.
76
+
77
-See the CONFIGURATION section for 'sendemail.multiEdit'.
77
+See the CONFIGURATION section for `sendemail.multiEdit`.
78
79
--from=<address>::
80
Specify the sender of the emails. If not specified on the command line,
81
- the value of the 'sendemail.from' configuration option is used. If
82
- neither the command-line option nor 'sendemail.from' are set, then the
81
+ the value of the `sendemail.from` configuration option is used. If
82
+ neither the command-line option nor `sendemail.from` are set, then the
83
user will be prompted for the value. The default for the prompt will be
84
the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not
85
set, as returned by "git var -l".
@@ -114,7 +114,7 @@ is not set, this will be prompted for.
114
--to=<address>,...::
115
Specify the primary recipient of the emails generated. Generally, this
116
will be the upstream maintainer of the project involved. Default is the
117
- value of the 'sendemail.to' configuration value; if that is unspecified,
117
+ value of the `sendemail.to` configuration value; if that is unspecified,
118
and --to-cmd is not specified, this will be prompted for.
119
+
120
This option may be specified multiple times.
@@ -138,7 +138,7 @@ Note that no attempts whatsoever are made to validate the encoding.
138
can be useful when the repository contains files that contain carriage
139
returns, but makes the raw patch email file (as saved from a MUA) much
140
harder to inspect manually. base64 is even more fool proof, but also
141
- even more opaque. Default is the value of the 'sendemail.transferEncoding'
141
+ even more opaque. Default is the value of the `sendemail.transferEncoding`
142
configuration value; if that is unspecified, git will use 8bit and not
143
add a Content-Transfer-Encoding header.
144
@@ -157,20 +157,20 @@ Sending
157
subscribed to a list. In order to use the 'From' address, set the
158
value to "auto". If you use the sendmail binary, you must have
159
suitable privileges for the -f parameter. Default is the value of the
160
- 'sendemail.envelopeSender' configuration variable; if that is
160
+ `sendemail.envelopeSender` configuration variable; if that is
161
unspecified, choosing the envelope sender is left to your MTA.
162
163
--smtp-encryption=<encryption>::
164
Specify the encryption to use, either 'ssl' or 'tls'. Any other
165
value reverts to plain SMTP. Default is the value of
166
- 'sendemail.smtpEncryption'.
166
+ `sendemail.smtpEncryption`.
167
168
--smtp-domain=<FQDN>::
169
Specifies the Fully Qualified Domain Name (FQDN) used in the
170
HELO/EHLO command to the SMTP server. Some servers require the
171
FQDN to match your IP address. If not set, git send-email attempts
172
to determine your FQDN automatically. Default is the value of
173
- 'sendemail.smtpDomain'.
173
+ `sendemail.smtpDomain`.
174
175
--smtp-auth=<mechanisms>::
176
Whitespace-separated list of allowed SMTP-AUTH mechanisms. This setting
@@ -188,13 +188,13 @@ is specified, all mechanisms supported by the SASL library can be used.
188
--smtp-pass[=<password>]::
189
Password for SMTP-AUTH. The argument is optional: If no
190
argument is specified, then the empty string is used as
191
- the password. Default is the value of 'sendemail.smtpPass',
191
+ the password. Default is the value of `sendemail.smtpPass`,
192
however '--smtp-pass' always overrides this value.
193
+
194
Furthermore, passwords need not be specified in configuration files
195
or on the command line. If a username has been specified (with
196
-'--smtp-user' or a 'sendemail.smtpUser'), but no password has been
197
-specified (with '--smtp-pass' or 'sendemail.smtpPass'), then
196
+'--smtp-user' or a `sendemail.smtpUser`), but no password has been
197
+specified (with '--smtp-pass' or `sendemail.smtpPass`), then
198
a password is obtained using 'git-credential'.
199
200
--smtp-server=<host>::
@@ -202,7 +202,7 @@ a password is obtained using 'git-credential'.
202
`smtp.example.com` or a raw IP address). Alternatively it can
203
specify a full pathname of a sendmail-like program instead;
204
the program must support the `-i` option. Default value can
205
- be specified by the 'sendemail.smtpServer' configuration
205
+ be specified by the `sendemail.smtpServer` configuration
206
option; the built-in default is `/usr/sbin/sendmail` or
207
`/usr/lib/sendmail` if such program is available, or
208
`localhost` otherwise.
@@ -213,11 +213,11 @@ a password is obtained using 'git-credential'.
213
submission port 587, or the common SSL smtp port 465);
214
symbolic port names (e.g. "submission" instead of 587)
215
are also accepted. The port can also be set with the
216
- 'sendemail.smtpServerPort' configuration variable.
216
+ `sendemail.smtpServerPort` configuration variable.
217
218
--smtp-server-option=<option>::
219
If set, specifies the outgoing SMTP server option to use.
220
- Default value can be specified by the 'sendemail.smtpServerOption'
220
+ Default value can be specified by the `sendemail.smtpServerOption`
221
configuration option.
222
+
223
The --smtp-server-option option must be repeated for each option you want
@@ -234,13 +234,13 @@ must be used for each option.
234
certificates concatenated together: see verify(1) -CAfile and
235
-CApath for more information on these). Set it to an empty string
236
to disable certificate verification. Defaults to the value of the
237
- 'sendemail.smtpsslcertpath' configuration variable, if set, or the
237
+ `sendemail.smtpsslcertpath` configuration variable, if set, or the
238
backing SSL library's compiled-in default otherwise (which should
239
be the best choice on most platforms).
240
241
--smtp-user=<user>::
242
- Username for SMTP-AUTH. Default is the value of 'sendemail.smtpUser';
243
- if a username is not specified (with '--smtp-user' or 'sendemail.smtpUser'),
242
+ Username for SMTP-AUTH. Default is the value of `sendemail.smtpUser`;
243
+ if a username is not specified (with '--smtp-user' or `sendemail.smtpUser`),
244
then authentication is not attempted.
245
246
--smtp-debug=0|1::
@@ -261,25 +261,25 @@ Automating
261
Specify a command to execute once per patch file which
262
should generate patch file specific "Cc:" entries.
263
Output of this command must be single email address per line.
264
- Default is the value of 'sendemail.ccCmd' configuration value.
264
+ Default is the value of `sendemail.ccCmd` configuration value.
265
266
--[no-]chain-reply-to::
267
If this is set, each email will be sent as a reply to the previous
268
email sent. If disabled with "--no-chain-reply-to", all emails after
269
the first will be sent as replies to the first email sent. When using
270
this, it is recommended that the first file given be an overview of the
271
- entire patch series. Disabled by default, but the 'sendemail.chainReplyTo'
271
+ entire patch series. Disabled by default, but the `sendemail.chainReplyTo`
272
configuration variable can be used to enable it.
273
274
--identity=<identity>::
275
A configuration identity. When given, causes values in the
276
'sendemail.<identity>' subsection to take precedence over
277
values in the 'sendemail' section. The default identity is
278
- the value of 'sendemail.identity'.
278
+ the value of `sendemail.identity`.
279
280
--[no-]signed-off-by-cc::
281
If this is set, add emails found in Signed-off-by: or Cc: lines to the
282
- cc list. Default is the value of 'sendemail.signedoffbycc' configuration
282
+ cc list. Default is the value of `sendemail.signedoffbycc` configuration
283
value; if that is unspecified, default to --signed-off-by-cc.
284
285
--[no-]cc-cover::
@@ -312,13 +312,13 @@ Automating
312
- 'all' will suppress all auto cc values.
313
--
314
+
315
-Default is the value of 'sendemail.suppresscc' configuration value; if
315
+Default is the value of `sendemail.suppresscc` configuration value; if
316
that is unspecified, default to 'self' if --suppress-from is
317
specified, as well as 'body' if --no-signed-off-cc is specified.
318
319
--[no-]suppress-from::
320
If this is set, do not add the From: address to the cc: list.
321
- Default is the value of 'sendemail.suppressFrom' configuration
321
+ Default is the value of `sendemail.suppressFrom` configuration
322
value; if that is unspecified, default to --no-suppress-from.
323
324
--[no-]thread::
@@ -330,7 +330,7 @@ specified, as well as 'body' if --no-signed-off-cc is specified.
330
+
331
If disabled with "--no-thread", those headers will not be added
332
(unless specified with --in-reply-to). Default is the value of the
333
-'sendemail.thread' configuration value; if that is unspecified,
333
+`sendemail.thread` configuration value; if that is unspecified,
334
default to --thread.
335
+
336
It is up to the user to ensure that no In-Reply-To header already
@@ -355,7 +355,7 @@ Administering
355
- 'auto' is equivalent to 'cc' + 'compose'
356
--
357
+
358
-Default is the value of 'sendemail.confirm' configuration value; if that
358
+Default is the value of `sendemail.confirm` configuration value; if that
359
is unspecified, default to 'auto' unless any of the suppress options
360
have been specified, in which case default to 'compose'.
361
@@ -381,7 +381,7 @@ have been specified, in which case default to 'compose'.
381
is due to SMTP limits as described by http://www.ietf.org/rfc/rfc2821.txt.
382
--
383
+
384
-Default is the value of 'sendemail.validate'; if this is not set,
384
+Default is the value of `sendemail.validate`; if this is not set,
385
default to '--validate'.
386
387
--force::
@@ -403,7 +403,7 @@ CONFIGURATION
403
404
sendemail.aliasesFile::
405
To avoid typing long email addresses, point this to one or more
406
- email aliases files. You must also supply 'sendemail.aliasFileType'.
406
+ email aliases files. You must also supply `sendemail.aliasFileType`.
407
408
sendemail.aliasFileType::
409
Format of the file(s) specified in sendemail.aliasesFile. Must be
Documentation/git-svn.txt
+1
-1
@@ -748,7 +748,7 @@ svn-remote.<name>.rewriteUUID::
748
749
svn-remote.<name>.pushurl::
750
751
- Similar to Git's 'remote.<name>.pushurl', this key is designed
751
+ Similar to Git's `remote.<name>.pushurl`, this key is designed
752
to be used in cases where 'url' points to an SVN repository
753
via a read-only transport, to provide an alternate read/write
754
transport. It is assumed that both keys point to the same
Documentation/git-tag.txt
+1
-1
@@ -104,7 +104,7 @@ OPTIONS
104
order can also be affected by the
105
"versionsort.prereleaseSuffix" configuration variable.
106
The keys supported are the same as those in `git for-each-ref`.
107
- Sort order defaults to the value configured for the 'tag.sort'
107
+ Sort order defaults to the value configured for the `tag.sort`
108
variable if it exists, or lexicographic order otherwise. See
109
linkgit:git-config[1].
110
Documentation/git-web--browse.txt
+3
-3
@@ -62,14 +62,14 @@ CONF.VAR (from -c option) and web.browser
62
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
63
64
The web browser can be specified using a configuration variable passed
65
-with the -c (or --config) command-line option, or the 'web.browser'
65
+with the -c (or --config) command-line option, or the `web.browser`
66
configuration variable if the former is not used.
67
68
browser.<tool>.path
69
~~~~~~~~~~~~~~~~~~~
70
71
You can explicitly provide a full path to your preferred browser by
72
-setting the configuration variable 'browser.<tool>.path'. For example,
72
+setting the configuration variable `browser.<tool>.path`. For example,
73
you can configure the absolute path to firefox by setting
74
'browser.firefox.path'. Otherwise, 'git web{litdd}browse' assumes the tool
75
is available in PATH.
@@ -79,7 +79,7 @@ browser.<tool>.cmd
79
80
When the browser, specified by options or configuration variables, is
81
not among the supported ones, then the corresponding
82
-'browser.<tool>.cmd' configuration variable will be looked up. If this
82
+`browser.<tool>.cmd` configuration variable will be looked up. If this
83
variable exists then 'git web{litdd}browse' will treat the specified tool
84
as a custom command and will use a shell eval to run the command with
85
the URLs passed as arguments.
Documentation/git.txt
+1
-1
@@ -991,7 +991,7 @@ for further details.
991
If this environment variable is set, then Git commands which need to
992
acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
993
will call this program with a suitable prompt as command-line argument
994
- and read the password from its STDOUT. See also the 'core.askPass'
994
+ and read the password from its STDOUT. See also the `core.askPass`
995
option in linkgit:git-config[1].
996
997
`GIT_TERMINAL_PROMPT`::
Documentation/gitignore.txt
+1
-1
@@ -38,7 +38,7 @@ precedence, the last matching pattern decides the outcome):
38
* Patterns read from `$GIT_DIR/info/exclude`.
39
40
* Patterns read from the file specified by the configuration
41
- variable 'core.excludesFile'.
41
+ variable `core.excludesFile`.
42
43
Which file to place a pattern in depends on how the pattern is meant to
44
be used.
Documentation/gitremote-helpers.txt
+2
-2
@@ -61,10 +61,10 @@ argument. If such a URL is encountered directly on the command line,
61
the first argument is '<address>', and if it is encountered in a
62
configured remote, the first argument is the name of that remote.
63
64
-Additionally, when a configured remote has 'remote.<name>.vcs' set to
64
+Additionally, when a configured remote has `remote.<name>.vcs` set to
65
'<transport>', Git explicitly invokes 'git remote-<transport>' with
66
'<name>' as the first argument. If set, the second argument is
67
-'remote.<name>.url'; otherwise, the second argument is omitted.
67
+`remote.<name>.url`; otherwise, the second argument is omitted.
68
69
INPUT FORMAT
70
------------
Documentation/pretty-options.txt
+2
-2
@@ -26,7 +26,7 @@ people using 80-column terminals.
26
--no-abbrev-commit::
27
Show the full 40-byte hexadecimal commit object name. This negates
28
`--abbrev-commit` and those options which imply it such as
29
- "--oneline". It also overrides the 'log.abbrevCommit' variable.
29
+ "--oneline". It also overrides the `log.abbrevCommit` variable.
30
31
--oneline::
32
This is a shorthand for "--pretty=oneline --abbrev-commit"
@@ -51,7 +51,7 @@ ifndef::git-rev-list[]
51
on the command line.
52
+
53
By default, the notes shown are from the notes refs listed in the
54
-'core.notesRef' and 'notes.displayRef' variables (or corresponding
54
+`core.notesRef` and `notes.displayRef` variables (or corresponding
55
environment overrides). See linkgit:git-config[1] for more details.
56
+
57
With an optional '<treeish>' argument, use the treeish to find the notes