Documentation: make environment variable formatting more consistent

Documentation/git.txt is not consistent in the way it stylizes mentions of Environment Variables. Most of them are enclosed in single quotes, some are enclosed in backticks, some are not enclosed. Signed-off-by: Andrey Rybak <rybak.a.v@gmail.com> Signed-off-by: Jeff King <peff@peff.net>

Андрей Рыбак committed Nov 11, 2015 at 18:47 UTC 6dedd8001b3b6b229f6620429918152bd263fb49
1 file changed +6 -6
Documentation/git.txt
+6 -6
@@ -1056,7 +1056,7 @@ of clones and fetches.
1056 cloning of shallow repositories.
1057 See 'GIT_TRACE' for available trace output options.
1058
1059 -GIT_LITERAL_PATHSPECS::
1059 +'GIT_LITERAL_PATHSPECS'::
1060 Setting this variable to `1` will cause Git to treat all
1061 pathspecs literally, rather than as glob patterns. For example,
1062 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
@@ -1065,15 +1065,15 @@ GIT_LITERAL_PATHSPECS::
1065 literal paths to Git (e.g., paths previously given to you by
1066 `git ls-tree`, `--raw` diff output, etc).
1067
1068 -GIT_GLOB_PATHSPECS::
1068 +'GIT_GLOB_PATHSPECS'::
1069 Setting this variable to `1` will cause Git to treat all
1070 pathspecs as glob patterns (aka "glob" magic).
1071
1072 -GIT_NOGLOB_PATHSPECS::
1072 +'GIT_NOGLOB_PATHSPECS'::
1073 Setting this variable to `1` will cause Git to treat all
1074 pathspecs as literal (aka "literal" magic).
1075
1076 -GIT_ICASE_PATHSPECS::
1076 +'GIT_ICASE_PATHSPECS'::
1077 Setting this variable to `1` will cause Git to treat all
1078 pathspecs as case-insensitive.
1079
@@ -1087,7 +1087,7 @@ GIT_ICASE_PATHSPECS::
1087 variable when it is invoked as the top level command by the
1088 end user, to be recorded in the body of the reflog.
1089
1090 -`GIT_REF_PARANOIA`::
1090 +'GIT_REF_PARANOIA'::
1091 If set to `1`, include broken or badly named refs when iterating
1092 over lists of refs. In a normal, non-corrupted repository, this
1093 does nothing. However, enabling it may help git to detect and
@@ -1098,7 +1098,7 @@ GIT_ICASE_PATHSPECS::
1098 an operation has touched every ref (e.g., because you are
1099 cloning a repository to make a backup).
1100
1101 -`GIT_ALLOW_PROTOCOL`::
1101 +'GIT_ALLOW_PROTOCOL'::
1102 If set, provide a colon-separated list of protocols which are
1103 allowed to be used with fetch/push/clone. This is useful to
1104 restrict recursive submodule initialization from an untrusted