{"thread":{"id":"42725","subject":"[PATCH 1/6] doc: typeset short command-line options as literal","startedAt":"2016-06-27T17:46:51Z","lastAt":"2016-06-30T06:42:51Z","messageCount":22,"participants":["Matthieu Moy","Jeff King","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":6},"messages":[{"id":"290259","messageId":"20160627174623.11084-1-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":null,"subject":"[PATCH 1/6] doc: typeset short command-line options as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-27T17:46:18Z","receivedAt":"2016-06-27T17:46:51Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"It was common in our documentation to surround short option names with\nforward quotes, which renders as italic in HTML. Instead, use backquotes\nwhich renders as monospace. This is one more step toward conformance to\nDocumentation/CodingGuidelines.\n\nThis was obtained with:\n\n  perl -pi -e \"s/'(-[a-z])'/\\`\\$1\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/config.txt              |  8 ++++----\n Documentation/diff-config.txt         |  2 +-\n Documentation/diff-format.txt         |  8 ++++----\n Documentation/diff-generate-patch.txt |  4 ++--\n Documentation/git-cat-file.txt        | 12 ++++++------\n Documentation/git-checkout.txt        |  4 ++--\n Documentation/git-clean.txt           |  2 +-\n Documentation/git-commit-tree.txt     |  2 +-\n Documentation/git-commit.txt          |  2 +-\n Documentation/git-cvsimport.txt       |  6 +++---\n Documentation/git-cvsserver.txt       |  8 ++++----\n Documentation/git-diff-tree.txt       | 14 +++++++-------\n Documentation/git-fetch-pack.txt      |  2 +-\n Documentation/git-filter-branch.txt   |  2 +-\n Documentation/git-grep.txt            |  2 +-\n Documentation/git-help.txt            |  4 ++--\n Documentation/git-ls-tree.txt         |  4 ++--\n Documentation/git-mktree.txt          |  2 +-\n Documentation/git-mv.txt              |  2 +-\n Documentation/git-notes.txt           |  2 +-\n Documentation/git-repack.txt          |  4 ++--\n Documentation/git-shell.txt           |  4 ++--\n Documentation/git.txt                 |  4 ++--\n 23 files changed, 52 insertions(+), 52 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex ef77f03..c483785 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -913,7 +913,7 @@ browser.<tool>.cmd::\n \n browser.<tool>.path::\n \tOverride the path for the given tool that may be used to\n-\tbrowse HTML help (see '-w' option in linkgit:git-help[1]) or a\n+\tbrowse HTML help (see `-w` option in linkgit:git-help[1]) or a\n \tworking repository in gitweb (see linkgit:git-instaweb[1]).\n \n clean.requireForce::\n@@ -1394,9 +1394,9 @@ gitcvs.logFile::\n \n gitcvs.usecrlfattr::\n \tIf true, the server will look up the end-of-line conversion\n-\tattributes for files to determine the '-k' modes to use. If\n+\tattributes for files to determine the `-k` modes to use. If\n \tthe attributes force Git to treat a file as text,\n-\tthe '-k' mode will be left blank so CVS clients will\n+\tthe `-k` mode will be left blank so CVS clients will\n \ttreat it as text. If they suppress text conversion, the file\n \twill be set with '-kb' mode, which suppresses any newline munging\n \tthe client might otherwise do. If the attributes do not allow\n@@ -1466,7 +1466,7 @@ gitweb.snapshot::\n \tSee linkgit:gitweb.conf[5] for description.\n \n grep.lineNumber::\n-\tIf set to true, enable '-n' option by default.\n+\tIf set to true, enable `-n` option by default.\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\ndiff --git a/Documentation/diff-config.txt b/Documentation/diff-config.txt\nindex 7513795..0ddb7a6 100644\n--- a/Documentation/diff-config.txt\n+++ b/Documentation/diff-config.txt\n@@ -105,7 +105,7 @@ diff.orderFile::\n \n diff.renameLimit::\n \tThe number of files to consider when performing the copy/rename\n-\tdetection; equivalent to the 'git diff' option '-l'.\n+\tdetection; equivalent to the 'git diff' option `-l`.\n \n diff.renames::\n \tTells Git to detect renames.  If set to any boolean value, it\ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\nindex 85b0890..f10fd54 100644\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -46,11 +46,11 @@ That is, from the left to the right:\n . sha1 for \"dst\"; 0\\{40\\} if creation, unmerged or \"look at work tree\".\n . a space.\n . status, followed by optional \"score\" number.\n-. a tab or a NUL when '-z' option is used.\n+. a tab or a NUL when `-z` option is used.\n . path for \"src\"\n-. a tab or a NUL when '-z' option is used; only exists for C or R.\n+. a tab or a NUL when `-z` option is used; only exists for C or R.\n . path for \"dst\"; only exists for C or R.\n-. an LF or a NUL when '-z' option is used, to terminate the record.\n+. an LF or a NUL when `-z` option is used, to terminate the record.\n \n Possible status letters are:\n \n@@ -86,7 +86,7 @@ diff format for merges\n ----------------------\n \n \"git-diff-tree\", \"git-diff-files\" and \"git-diff --raw\"\n-can take '-c' or '--cc' option\n+can take `-c` or '--cc' option\n to generate diff output also for merge commits.  The output differs\n from the format described above in the following way:\n \ndiff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt\nindex c91afee..18608f5 100644\n--- a/Documentation/diff-generate-patch.txt\n+++ b/Documentation/diff-generate-patch.txt\n@@ -2,7 +2,7 @@ Generating patches with -p\n --------------------------\n \n When \"git-diff-index\", \"git-diff-tree\", or \"git-diff-files\" are run\n-with a '-p' option, \"git diff\" without the '--raw' option, or\n+with a `-p` option, \"git diff\" without the '--raw' option, or\n \"git log\" with the \"-p\" option, they\n do not produce the output described above; instead they produce a\n patch file.  You can customize the creation of such patches via the\n@@ -114,7 +114,7 @@ index fabadb8,cc95eb0..4866510\n ------------\n \n 1.   It is preceded with a \"git diff\" header, that looks like\n-     this (when '-c' option is used):\n+     this (when `-c` option is used):\n \n        diff --combined file\n +\ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex eb3d694..f8d0dcf 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -15,8 +15,8 @@ SYNOPSIS\n DESCRIPTION\n -----------\n In its first form, the command provides the content or the type of an object in\n-the repository. The type is required unless '-t' or '-p' is used to find the\n-object type, or '-s' is used to find the object size, or '--textconv' is used\n+the repository. The type is required unless `-t` or `-p` is used to find the\n+object type, or `-s` is used to find the object size, or '--textconv' is used\n (which implies type \"blob\").\n \n In the second form, a list of objects (separated by linefeeds) is provided on\n@@ -144,13 +144,13 @@ respectively print:\n \n OUTPUT\n ------\n-If '-t' is specified, one of the <type>.\n+If `-t` is specified, one of the <type>.\n \n-If '-s' is specified, the size of the <object> in bytes.\n+If `-s` is specified, the size of the <object> in bytes.\n \n-If '-e' is specified, no output.\n+If `-e` is specified, no output.\n \n-If '-p' is specified, the contents of <object> are pretty-printed.\n+If `-p` is specified, the contents of <object> are pretty-printed.\n \n If <type> is specified, the raw (though uncompressed) contents of the <object>\n will be returned.\ndiff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\nindex 5e5273e..7a2201b 100644\n--- a/Documentation/git-checkout.txt\n+++ b/Documentation/git-checkout.txt\n@@ -157,7 +157,7 @@ of it\").\n \tWhen creating a new branch, set up \"upstream\" configuration. See\n \t\"--track\" in linkgit:git-branch[1] for details.\n +\n-If no '-b' option is given, the name of the new branch will be\n+If no `-b` option is given, the name of the new branch will be\n derived from the remote-tracking branch, by looking at the local part of\n the refspec configured for the corresponding remote, and then stripping\n the initial part up to the \"*\".\n@@ -165,7 +165,7 @@ This would tell us to use \"hack\" as the local branch when branching\n off of \"origin/hack\" (or \"remotes/origin/hack\", or even\n \"refs/remotes/origin/hack\").  If the given name has no slash, or the above\n guessing results in an empty name, the guessing is aborted.  You can\n-explicitly give a name with '-b' in such a case.\n+explicitly give a name with `-b` in such a case.\n \n --no-track::\n \tDo not set up \"upstream\" configuration, even if the\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 51a7e26..03056da 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -16,7 +16,7 @@ DESCRIPTION\n Cleans the working tree by recursively removing files that are not\n under version control, starting from the current directory.\n \n-Normally, only files unknown to Git are removed, but if the '-x'\n+Normally, only files unknown to Git are removed, but if the `-x`\n option is specified, ignored files are also removed. This can, for\n example, be useful to remove all build products.\n \ndiff --git a/Documentation/git-commit-tree.txt b/Documentation/git-commit-tree.txt\nindex 48c33d7..ff13025 100644\n--- a/Documentation/git-commit-tree.txt\n+++ b/Documentation/git-commit-tree.txt\n@@ -44,7 +44,7 @@ OPTIONS\n \tAn existing tree object\n \n -p <parent>::\n-\tEach '-p' indicates the id of a parent commit object.\n+\tEach `-p` indicates the id of a parent commit object.\n \n -m <message>::\n \tA paragraph in the commit log message. This can be given more than\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex 19ee2dd..2afda81 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -75,7 +75,7 @@ OPTIONS\n \n -c <commit>::\n --reedit-message=<commit>::\n-\tLike '-C', but with '-c' the editor is invoked, so that\n+\tLike '-C', but with `-c` the editor is invoked, so that\n \tthe user can further edit the commit message.\n \n --fixup=<commit>::\ndiff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt\nindex 00a0679..bbf1c2b 100644\n--- a/Documentation/git-cvsimport.txt\n+++ b/Documentation/git-cvsimport.txt\n@@ -103,7 +103,7 @@ the old cvs2git tool.\n \n -p <options-for-cvsps>::\n \tAdditional options for cvsps.\n-\tThe options '-u' and '-A' are implicit and should not be used here.\n+\tThe options `-u` and '-A' are implicit and should not be used here.\n +\n If you need to pass multiple options, separate them with a comma.\n \n@@ -122,7 +122,7 @@ If you need to pass multiple options, separate them with a comma.\n \n -M <regex>::\n \tAttempt to detect merges based on the commit message with a custom\n-\tregex. It can be used with '-m' to enable the default regexes\n+\tregex. It can be used with `-m` to enable the default regexes\n \tas well. You must escape forward slashes.\n +\n The regex must capture the source branch name in $1.\n@@ -186,7 +186,7 @@ messages, bug-tracking systems, email archives, and the like.\n \n OUTPUT\n ------\n-If '-v' is specified, the script reports what it is doing.\n+If `-v` is specified, the script reports what it is doing.\n \n Otherwise, success is indicated the Unix way, i.e. by simply exiting with\n a zero exit status.\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex db4d7a9..5e3c6a8 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -402,12 +402,12 @@ Exports and tagging (tags and branches) are not supported at this stage.\n CRLF Line Ending Conversions\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n-By default the server leaves the '-k' mode blank for all files,\n+By default the server leaves the `-k` mode blank for all files,\n which causes the CVS client to treat them as a text files, subject\n to end-of-line conversion on some platforms.\n \n You can make the server use the end-of-line conversion attributes to\n-set the '-k' modes for files by setting the `gitcvs.usecrlfattr`\n+set the `-k` modes for files by setting the `gitcvs.usecrlfattr`\n config variable.  See linkgit:gitattributes[5] for more information\n about end-of-line conversion.\n \n@@ -415,9 +415,9 @@ Alternatively, if `gitcvs.usecrlfattr` config is not enabled\n or the attributes do not allow automatic detection for a filename, then\n the server uses the `gitcvs.allBinary` config for the default setting.\n If `gitcvs.allBinary` is set, then file not otherwise\n-specified will default to '-kb' mode. Otherwise the '-k' mode\n+specified will default to '-kb' mode. Otherwise the `-k` mode\n is left blank. But if `gitcvs.allBinary` is set to \"guess\", then\n-the correct '-k' mode will be guessed based on the contents of\n+the correct `-k` mode will be guessed based on the contents of\n the file.\n \n For best consistency with 'cvs', it is probably best to override the\ndiff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt\nindex 1439486..7558e49 100644\n--- a/Documentation/git-diff-tree.txt\n+++ b/Documentation/git-diff-tree.txt\n@@ -70,13 +70,13 @@ commits (but not trees).\n \tBy default, 'git diff-tree --stdin' does not show\n \tdifferences for merge commits.  With this flag, it shows\n \tdifferences to that commit from all of its parents. See\n-\talso '-c'.\n+\talso `-c`.\n \n -s::\n \tBy default, 'git diff-tree --stdin' shows differences,\n-\teither in machine-readable form (without '-p') or in patch\n-\tform (with '-p').  This output can be suppressed.  It is\n-\tonly useful with '-v' flag.\n+\teither in machine-readable form (without `-p`) or in patch\n+\tform (with `-p`).  This output can be suppressed.  It is\n+\tonly useful with `-v` flag.\n \n -v::\n \tThis flag causes 'git diff-tree --stdin' to also show\n@@ -94,14 +94,14 @@ include::pretty-options.txt[]\n \tone <tree-ish>, or '--stdin').  It shows the differences\n \tfrom each of the parents to the merge result simultaneously\n \tinstead of showing pairwise diff between a parent and the\n-\tresult one at a time (which is what the '-m' option does).\n+\tresult one at a time (which is what the `-m` option does).\n \tFurthermore, it lists only files which were modified\n \tfrom all parents.\n \n --cc::\n \tThis flag changes the way a merge commit patch is displayed,\n-\tin a similar way to the '-c' option. It implies the '-c'\n-\tand '-p' options and further compresses the patch output\n+\tin a similar way to the `-c` option. It implies the `-c`\n+\tand `-p` options and further compresses the patch output\n \tby omitting uninteresting hunks whose the contents in the parents\n \thave only two variants and the merge result picks one of them\n \twithout modification.  When all hunks are uninteresting, the commit\ndiff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt\nindex 239623c..4c8219d 100644\n--- a/Documentation/git-fetch-pack.txt\n+++ b/Documentation/git-fetch-pack.txt\n@@ -47,7 +47,7 @@ be in a separate packet, and the list must end with a flush packet.\n \n -q::\n --quiet::\n-\tPass '-q' flag to 'git unpack-objects'; this makes the\n+\tPass `-q` flag to 'git unpack-objects'; this makes the\n \tcloning process less verbose.\n \n -k::\ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex bd560d3..2d30297 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -52,7 +52,7 @@ if different from the rewritten ones, will be stored in the namespace\n \n Note that since this operation is very I/O expensive, it might\n be a good idea to redirect the temporary directory off-disk with the\n-'-d' option, e.g. on tmpfs.  Reportedly the speedup is very noticeable.\n+`-d` option, e.g. on tmpfs.  Reportedly the speedup is very noticeable.\n \n \n Filters\ndiff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt\nindex 40cfe37..557973b 100644\n--- a/Documentation/git-grep.txt\n+++ b/Documentation/git-grep.txt\n@@ -41,7 +41,7 @@ CONFIGURATION\n -------------\n \n grep.lineNumber::\n-\tIf set to true, enable '-n' option by default.\n+\tIf set to true, enable `-n` option by default.\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\ndiff --git a/Documentation/git-help.txt b/Documentation/git-help.txt\nindex 338b8d6..c6f7ce7 100644\n--- a/Documentation/git-help.txt\n+++ b/Documentation/git-help.txt\n@@ -18,10 +18,10 @@ With no options and no COMMAND or GUIDE given, the synopsis of the 'git'\n command and a list of the most commonly used Git commands are printed\n on the standard output.\n \n-If the option '--all' or '-a' is given, all available commands are\n+If the option '--all' or `-a` is given, all available commands are\n printed on the standard output.\n \n-If the option '--guide' or '-g' is given, a list of the useful\n+If the option '--guide' or `-g` is given, a list of the useful\n Git guides is also printed on the standard output.\n \n If a command, or a guide, is given, a manual page for that command or\ndiff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt\nindex 16e87fd..a9f1909 100644\n--- a/Documentation/git-ls-tree.txt\n+++ b/Documentation/git-ls-tree.txt\n@@ -20,7 +20,7 @@ in the current working directory.  Note that:\n \n  - the behaviour is slightly different from that of \"/bin/ls\" in that the\n    '<path>' denotes just a list of patterns to match, e.g. so specifying\n-   directory name (without '-r') will behave differently, and order of the\n+   directory name (without `-r`) will behave differently, and order of the\n    arguments does not matter.\n \n  - the behaviour is similar to that of \"/bin/ls\" in that the '<path>' is\n@@ -46,7 +46,7 @@ OPTIONS\n \n -t::\n \tShow tree entries even when going to recurse them. Has no effect\n-\tif '-r' was not passed. '-d' implies '-t'.\n+\tif `-r` was not passed. `-d` implies `-t`.\n \n -l::\n --long::\ndiff --git a/Documentation/git-mktree.txt b/Documentation/git-mktree.txt\nindex 5c6ebdf..c3616e7 100644\n--- a/Documentation/git-mktree.txt\n+++ b/Documentation/git-mktree.txt\n@@ -32,7 +32,7 @@ OPTIONS\n --batch::\n \tAllow building of more than one tree object before exiting.  Each\n \ttree is separated by as single blank line. The final new-line is\n-\toptional.  Note - if the '-z' option is used, lines are terminated\n+\toptional.  Note - if the `-z` option is used, lines are terminated\n \twith NUL.\n \n GIT\ndiff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt\nindex e453132..cbae886 100644\n--- a/Documentation/git-mv.txt\n+++ b/Documentation/git-mv.txt\n@@ -35,7 +35,7 @@ OPTIONS\n         Skip move or rename actions which would lead to an error\n \tcondition. An error happens when a source is neither existing nor\n \tcontrolled by Git, or when it would overwrite an existing\n-        file unless '-f' is given.\n+        file unless `-f` is given.\n -n::\n --dry-run::\n \tDo nothing; only show what would happen\ndiff --git a/Documentation/git-notes.txt b/Documentation/git-notes.txt\nindex 02a10bc..be7db30 100644\n--- a/Documentation/git-notes.txt\n+++ b/Documentation/git-notes.txt\n@@ -152,7 +152,7 @@ OPTIONS\n \n -c <object>::\n --reedit-message=<object>::\n-\tLike '-C', but with '-c' the editor is invoked, so that\n+\tLike '-C', but with `-c` the editor is invoked, so that\n \tthe user can further edit the note message.\n \n --allow-empty::\ndiff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt\nindex b9c02ce..0c03eec 100644\n--- a/Documentation/git-repack.txt\n+++ b/Documentation/git-repack.txt\n@@ -33,7 +33,7 @@ OPTIONS\n \tpack everything referenced into a single pack.\n \tEspecially useful when packing a repository that is used\n \tfor private development. Use\n-\twith '-d'.  This will clean up the objects that `git prune`\n+\twith `-d`.  This will clean up the objects that `git prune`\n \tleaves behind, but `git fsck --full --dangling` shows as\n \tdangling.\n +\n@@ -42,7 +42,7 @@ whole new pack in order to get any contained object, no matter how many\n other objects in that pack they already have locally.\n \n -A::\n-\tSame as `-a`, unless '-d' is used.  Then any unreachable\n+\tSame as `-a`, unless `-d` is used.  Then any unreachable\n \tobjects in a previous pack become loose, unpacked objects,\n \tinstead of being left in the old pack.  Unreachable objects\n \tare never intentionally added to a pack, even when repacking.\ndiff --git a/Documentation/git-shell.txt b/Documentation/git-shell.txt\nindex e4bdd22..2e30a3e 100644\n--- a/Documentation/git-shell.txt\n+++ b/Documentation/git-shell.txt\n@@ -24,7 +24,7 @@ named `git-shell-commands` in the user's home directory.\n COMMANDS\n --------\n \n-'git shell' accepts the following commands after the '-c' option:\n+'git shell' accepts the following commands after the `-c` option:\n \n 'git receive-pack <argument>'::\n 'git upload-pack <argument>'::\n@@ -43,7 +43,7 @@ directory.\n INTERACTIVE USE\n ---------------\n \n-By default, the commands above can be executed only with the '-c'\n+By default, the commands above can be executed only with the `-c`\n option; the shell is not interactive.\n \n If a `~/git-shell-commands` directory is present, 'git shell'\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex 25ef006..24efc63 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -508,7 +508,7 @@ OPTIONS\n \n --help::\n \tPrints the synopsis and a list of the most commonly used\n-\tcommands. If the option '--all' or '-a' is given then all\n+\tcommands. If the option '--all' or `-a` is given then all\n \tavailable commands are printed. If a Git command is named this\n \toption will bring up the manual page for that command.\n +\n@@ -974,7 +974,7 @@ other\n \tThe command will be given exactly two or four arguments: the\n \t'username@host' (or just 'host') from the URL and the shell\n \tcommand to execute on that remote system, optionally preceded by\n-\t'-p' (literally) and the 'port' from the URL when it specifies\n+\t`-p` (literally) and the 'port' from the URL when it specifies\n \tsomething other than the default SSH port.\n +\n `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290260","messageId":"20160627174623.11084-3-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"[PATCH 3/6] doc: typeset -- as litteral","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-27T17:46:20Z","receivedAt":"2016-06-27T17:46:58Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"This was obtained with\n\n  perl -pi -e \"s/'--'/\\`--\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-fast-import.txt   | 4 ++--\n Documentation/git-filter-branch.txt | 2 +-\n Documentation/rev-list-options.txt  | 2 +-\n 3 files changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt\nindex 66910aa..c105f21 100644\n--- a/Documentation/git-fast-import.txt\n+++ b/Documentation/git-fast-import.txt\n@@ -1054,7 +1054,7 @@ relative-marks::\n no-relative-marks::\n force::\n \tAct as though the corresponding command-line option with\n-\ta leading '--' was passed on the command line\n+\ta leading `--` was passed on the command line\n \t(see OPTIONS, above).\n \n import-marks::\n@@ -1105,7 +1105,7 @@ options the user may specify to git fast-import itself.\n \n The `<option>` part of the command may contain any of the options\n listed in the OPTIONS section that do not change import semantics,\n-without the leading '--' and is treated in the same way.\n+without the leading `--` and is treated in the same way.\n \n Option commands must be the first commands on the input (not counting\n feature commands), to give an option command after any non-option\ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex 060ebb3..0a09698 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -197,7 +197,7 @@ to other tags will be rewritten to point to the underlying commit.\n <rev-list options>...::\n \tArguments for 'git rev-list'.  All positive refs included by\n \tthese options are rewritten.  You may also specify options\n-\tsuch as `--all`, but you must use '--' to separate them from\n+\tsuch as `--all`, but you must use `--` to separate them from\n \tthe 'git filter-branch' options. Implies <<Remap_to_ancestor>>.\n \n \ndiff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt\nindex 4f009d4..c5bd218 100644\n--- a/Documentation/rev-list-options.txt\n+++ b/Documentation/rev-list-options.txt\n@@ -193,7 +193,7 @@ endif::git-rev-list[]\n \n --stdin::\n \tIn addition to the '<commit>' listed on the command\n-\tline, read them from the standard input. If a '--' separator is\n+\tline, read them from the standard input. If a `--` separator is\n \tseen, stop reading commits and start reading paths to limit the\n \tresult.\n \n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290261","messageId":"20160627174623.11084-4-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"[PATCH 4/6] doc: typeset long options with argument as litteral","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-27T17:46:21Z","receivedAt":"2016-06-27T17:47:11Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"We previously reformatted '--option' to `--option`. This patch reformats\n'--option <arg>' to `--option <arg>`. Obtained with\n\n  perl -pi -e \"s/'(--[a-z][a-z=<>-]* <[^>]*>)'/\\`\\$1\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-config.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex 79905fb..f163113 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -47,12 +47,12 @@ checks or transformations are performed on the value.\n \n When reading, the values are read from the system, global and\n repository local configuration files by default, and options\n-`--system`, `--global`, `--local` and '--file <filename>' can be\n+`--system`, `--global`, `--local` and `--file <filename>` can be\n used to tell the command to read from only that location (see <<FILES>>).\n \n When writing, the new value is written to the repository local\n configuration file by default, and options `--system`, `--global`,\n-'--file <filename>' can be used to tell the command to write to\n+`--file <filename>` can be used to tell the command to write to\n that location (you can say `--local` but that is the default).\n \n This command will fail with non-zero status upon error.  Some exit\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290262","messageId":"20160627174623.11084-5-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"[PATCH 5/6] CodingGuidelines: formatting HEAD in documentation","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-27T17:46:22Z","receivedAt":"2016-06-27T17:47:14Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"The current practice is:\n\ngit/Documentation$ git grep \"'HEAD'\" | wc -l\n24\ngit/Documentation$ git grep \"\\`HEAD\\`\" | wc -l\n66\n\nLet's adopt the majority as a guideline.\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/CodingGuidelines | 5 +++--\n 1 file changed, 3 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\nindex 7f4769a..4cd95da 100644\n--- a/Documentation/CodingGuidelines\n+++ b/Documentation/CodingGuidelines\n@@ -527,12 +527,13 @@ Writing Documentation:\n  or commands:\n \n  Literal examples (e.g. use of command-line options, command names,\n- configuration and environment variables) must be typeset in monospace (i.e.\n- wrapped with backticks):\n+ branch names, configuration and environment variables) must be\n+ typeset in monospace (i.e. wrapped with backticks):\n    `--pretty=oneline`\n    `git rev-list`\n    `remote.pushDefault`\n    `GIT_DIR`\n+   `HEAD`\n \n  An environment variable must be prefixed with \"$\" only when referring to its\n  value and not when referring to the variable itself, in this case there is\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290263","messageId":"20160627174623.11084-6-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"[PATCH 6/6] doc: typeset HEAD and variants as litteral","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-27T17:46:23Z","receivedAt":"2016-06-27T17:47:15Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"This is an application of the newly added CodingGuidelines to HEAD and\nvariants like FETCH_HEAD. It was obtained with:\n\n  perl -pi -e \"s/'([A-Z_]*HEAD)'/\\`\\$1\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-bisect.txt        |  2 +-\n Documentation/git-branch.txt        |  4 ++--\n Documentation/git-cvsimport.txt     |  6 +++---\n Documentation/git-cvsserver.txt     |  2 +-\n Documentation/git-daemon.txt        |  2 +-\n Documentation/git-gui.txt           |  2 +-\n Documentation/git-ls-tree.txt       |  4 ++--\n Documentation/git-p4.txt            |  2 +-\n Documentation/git-tag.txt           |  2 +-\n Documentation/gitremote-helpers.txt |  2 +-\n Documentation/revisions.txt         | 24 ++++++++++++------------\n 11 files changed, 26 insertions(+), 26 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex d9f960b..2bb9a57 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -358,7 +358,7 @@ OPTIONS\n --no-checkout::\n +\n Do not checkout the new working tree at each iteration of the bisection\n-process. Instead just update a special reference named 'BISECT_HEAD' to make\n+process. Instead just update a special reference named `BISECT_HEAD` to make\n it point to the commit that should be tested.\n +\n This option may be useful when the test you would perform in each step\ndiff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt\nindex 123144f..1fe7344 100644\n--- a/Documentation/git-branch.txt\n+++ b/Documentation/git-branch.txt\n@@ -39,10 +39,10 @@ named commit).  With `--merged`, only branches merged into the named\n commit (i.e. the branches whose tip commits are reachable from the named\n commit) will be listed.  With `--no-merged` only branches not merged into\n the named commit will be listed.  If the <commit> argument is missing it\n-defaults to 'HEAD' (i.e. the tip of the current branch).\n+defaults to `HEAD` (i.e. the tip of the current branch).\n \n The command's second form creates a new branch head named <branchname>\n-which points to the current 'HEAD', or <start-point> if given.\n+which points to the current `HEAD`, or <start-point> if given.\n \n Note that this will create the new branch, but it will not switch the\n working tree to it; use \"git checkout <newbranch>\" to switch to the\ndiff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt\nindex bbf1c2b..41207a2 100644\n--- a/Documentation/git-cvsimport.txt\n+++ b/Documentation/git-cvsimport.txt\n@@ -74,10 +74,10 @@ OPTIONS\n \takin to the way 'git clone' uses 'origin' by default.\n \n -o <branch-for-HEAD>::\n-\tWhen no remote is specified (via -r) the 'HEAD' branch\n+\tWhen no remote is specified (via -r) the `HEAD` branch\n \tfrom CVS is imported to the 'origin' branch within the Git\n-\trepository, as 'HEAD' already has a special meaning for Git.\n-\tWhen a remote is specified the 'HEAD' branch is named\n+\trepository, as `HEAD` already has a special meaning for Git.\n+\tWhen a remote is specified the `HEAD` branch is named\n \tremotes/<remote>/master mirroring 'git clone' behaviour.\n \tUse this option if you want to import into a different\n \tbranch.\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex a1a5234..a336ae5 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -332,7 +332,7 @@ To get a checkout with the Eclipse CVS client:\n 3. Browse the 'modules' available. It will give you a list of the heads in\n    the repository. You will not be able to browse the tree from there. Only\n    the heads.\n-4. Pick 'HEAD' when it asks what branch/tag to check out. Untick the\n+4. Pick `HEAD` when it asks what branch/tag to check out. Untick the\n    \"launch commit wizard\" to avoid committing the .project file.\n \n Protocol notes: If you are using anonymous access via pserver, just select that.\ndiff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt\nindex 7901c54..3c91db7 100644\n--- a/Documentation/git-daemon.txt\n+++ b/Documentation/git-daemon.txt\n@@ -296,7 +296,7 @@ they correspond to these IP addresses.\n selectively enable/disable services per repository::\n \tTo enable 'git archive --remote' and disable 'git fetch' against\n \ta repository, have the following in the configuration file in the\n-\trepository (that is the file 'config' next to 'HEAD', 'refs' and\n+\trepository (that is the file 'config' next to `HEAD`, 'refs' and\n \t'objects').\n +\n ----------------------------------------------------------------\ndiff --git a/Documentation/git-gui.txt b/Documentation/git-gui.txt\nindex 8144527..c1a3e8b 100644\n--- a/Documentation/git-gui.txt\n+++ b/Documentation/git-gui.txt\n@@ -35,7 +35,7 @@ blame::\n \n browser::\n \tStart a tree browser showing all files in the specified\n-\tcommit (or 'HEAD' by default).  Files selected through the\n+\tcommit (or `HEAD` by default).  Files selected through the\n \tbrowser are opened in the blame viewer.\n \n citool::\ndiff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt\nindex a9f1909..dbc91f9 100644\n--- a/Documentation/git-ls-tree.txt\n+++ b/Documentation/git-ls-tree.txt\n@@ -27,9 +27,9 @@ in the current working directory.  Note that:\n    taken as relative to the current working directory.  E.g. when you are\n    in a directory 'sub' that has a directory 'dir', you can run 'git\n    ls-tree -r HEAD dir' to list the contents of the tree (that is\n-   'sub/dir' in 'HEAD').  You don't want to give a tree that is not at the\n+   'sub/dir' in `HEAD`).  You don't want to give a tree that is not at the\n    root level (e.g. `git ls-tree -r HEAD:sub dir`) in this case, as that\n-   would result in asking for 'sub/sub/dir' in the 'HEAD' commit.\n+   would result in asking for 'sub/sub/dir' in the `HEAD` commit.\n    However, the current working directory can be ignored by passing\n    --full-tree option.\n \ndiff --git a/Documentation/git-p4.txt b/Documentation/git-p4.txt\nindex 2703648..ac7e6a3 100644\n--- a/Documentation/git-p4.txt\n+++ b/Documentation/git-p4.txt\n@@ -275,7 +275,7 @@ These options can be used to modify 'git p4 submit' behavior.\n --origin <commit>::\n \tUpstream location from which commits are identified to submit to\n \tp4.  By default, this is the most recent p4 commit reachable\n-\tfrom 'HEAD'.\n+\tfrom `HEAD`.\n \n -M::\n \tDetect renames.  See linkgit:git-diff[1].  Renames will be\ndiff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt\nindex 499df56..dfd6b27 100644\n--- a/Documentation/git-tag.txt\n+++ b/Documentation/git-tag.txt\n@@ -167,7 +167,7 @@ This option is only applicable when listing tags without annotation lines.\n \n --[no-]merged [<commit>]::\n \tOnly list tags whose tips are reachable, or not reachable\n-\tif `--no-merged` is used, from the specified commit ('HEAD'\n+\tif `--no-merged` is used, from the specified commit (`HEAD`\n \tif not specified).\n \n CONFIGURATION\ndiff --git a/Documentation/gitremote-helpers.txt b/Documentation/gitremote-helpers.txt\nindex 53ce1d0..a4de50a 100644\n--- a/Documentation/gitremote-helpers.txt\n+++ b/Documentation/gitremote-helpers.txt\n@@ -298,7 +298,7 @@ Supported if the helper has the \"fetch\" capability.\n \tis followed by a blank line). For example, the following would\n \tbe two batches of 'push', the first asking the remote-helper\n \tto push the local ref 'master' to the remote ref 'master' and\n-\tthe local 'HEAD' to the remote 'branch', and the second\n+\tthe local `HEAD` to the remote 'branch', and the second\n \tasking to push ref 'foo' to ref 'bar' (forced update requested\n \tby the '+').\n +\ndiff --git a/Documentation/revisions.txt b/Documentation/revisions.txt\nindex 15879b3..abae363 100644\n--- a/Documentation/revisions.txt\n+++ b/Documentation/revisions.txt\n@@ -28,8 +28,8 @@ blobs contained in a commit.\n   first match in the following rules:\n \n   . If '$GIT_DIR/<refname>' exists, that is what you mean (this is usually\n-    useful only for 'HEAD', 'FETCH_HEAD', 'ORIG_HEAD', 'MERGE_HEAD'\n-    and 'CHERRY_PICK_HEAD');\n+    useful only for `HEAD`, `FETCH_HEAD`, `ORIG_HEAD`, `MERGE_HEAD`\n+    and `CHERRY_PICK_HEAD`);\n \n   . otherwise, 'refs/<refname>' if it exists;\n \n@@ -41,16 +41,16 @@ blobs contained in a commit.\n \n   . otherwise, 'refs/remotes/<refname>/HEAD' if it exists.\n +\n-'HEAD' names the commit on which you based the changes in the working tree.\n-'FETCH_HEAD' records the branch which you fetched from a remote repository\n+`HEAD` names the commit on which you based the changes in the working tree.\n+`FETCH_HEAD` records the branch which you fetched from a remote repository\n with your last `git fetch` invocation.\n-'ORIG_HEAD' is created by commands that move your 'HEAD' in a drastic\n-way, to record the position of the 'HEAD' before their operation, so that\n+`ORIG_HEAD` is created by commands that move your `HEAD` in a drastic\n+way, to record the position of the `HEAD` before their operation, so that\n you can easily change the tip of the branch back to the state before you ran\n them.\n-'MERGE_HEAD' records the commit(s) which you are merging into your branch\n+`MERGE_HEAD` records the commit(s) which you are merging into your branch\n when you run `git merge`.\n-'CHERRY_PICK_HEAD' records the commit which you are cherry-picking\n+`CHERRY_PICK_HEAD` records the commit which you are cherry-picking\n when you run `git cherry-pick`.\n +\n Note that any of the 'refs/*' cases above may come either from\n@@ -59,7 +59,7 @@ While the ref name encoding is unspecified, UTF-8 is preferred as\n some output processing may assume ref names in UTF-8.\n \n '@'::\n-  '@' alone is a shortcut for 'HEAD'.\n+  '@' alone is a shortcut for `HEAD`.\n \n '<refname>@{<date>}', e.g. 'master@\\{yesterday\\}', 'HEAD@{5 minutes ago}'::\n   A ref followed by the suffix '@' with a date specification\n@@ -101,7 +101,7 @@ some output processing may assume ref names in UTF-8.\n '<branchname>@\\{push\\}', e.g. 'master@\\{push\\}', '@\\{push\\}'::\n   The suffix '@\\{push}' reports the branch \"where we would push to\" if\n   `git push` were run while `branchname` was checked out (or the current\n-  'HEAD' if no branchname is specified). Since our push destination is\n+  `HEAD` if no branchname is specified). Since our push destination is\n   in a remote repository, of course, we report the local tracking branch\n   that corresponds to that branch (i.e., something in 'refs/remotes/').\n +\n@@ -283,12 +283,12 @@ To summarize:\n '<rev1>..<rev2>'::\n \tInclude commits that are reachable from <rev2> but exclude\n \tthose that are reachable from <rev1>.  When either <rev1> or\n-\t<rev2> is omitted, it defaults to 'HEAD'.\n+\t<rev2> is omitted, it defaults to `HEAD`.\n \n '<rev1>\\...<rev2>'::\n \tInclude commits that are reachable from either <rev1> or\n \t<rev2> but exclude those that are reachable from both.  When\n-\teither <rev1> or <rev2> is omitted, it defaults to 'HEAD'.\n+\teither <rev1> or <rev2> is omitted, it defaults to `HEAD`.\n \n '<rev>{caret}@', e.g. 'HEAD{caret}@'::\n   A suffix '{caret}' followed by an at sign is the same as listing\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290264","messageId":"20160627174623.11084-2-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"[PATCH 2/6] doc: typeset long command-line options as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-27T17:46:19Z","receivedAt":"2016-06-27T17:47:18Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Similarly to the previous commit, use backquotes instead of\nforward-quotes, for long options.\n\nThis was obtained with:\n\n  perl -pi -e \"s/'(--[a-z][a-z=<>-]*)'/\\`\\$1\\`/g\" *.txt\n\nand manual tweak to remove false positive in ascii-art (o'--o'--o' to\ndescribe rewritten history).\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/config.txt                 | 34 ++++++++++++++++----------------\n Documentation/diff-format.txt            |  2 +-\n Documentation/diff-generate-patch.txt    |  4 ++--\n Documentation/fetch-options.txt          |  6 +++---\n Documentation/git-am.txt                 |  4 ++--\n Documentation/git-branch.txt             |  2 +-\n Documentation/git-cat-file.txt           |  2 +-\n Documentation/git-cherry-pick.txt        |  2 +-\n Documentation/git-commit.txt             |  2 +-\n Documentation/git-config.txt             | 26 ++++++++++++------------\n Documentation/git-credential-store.txt   |  2 +-\n Documentation/git-cvsserver.txt          |  2 +-\n Documentation/git-daemon.txt             |  6 +++---\n Documentation/git-describe.txt           |  2 +-\n Documentation/git-diff-index.txt         |  4 ++--\n Documentation/git-diff-tree.txt          |  6 +++---\n Documentation/git-difftool.txt           |  2 +-\n Documentation/git-fetch-pack.txt         |  2 +-\n Documentation/git-filter-branch.txt      |  4 ++--\n Documentation/git-for-each-ref.txt       |  2 +-\n Documentation/git-fsck.txt               |  2 +-\n Documentation/git-grep.txt               |  8 ++++----\n Documentation/git-help.txt               |  6 +++---\n Documentation/git-http-push.txt          |  4 ++--\n Documentation/git-interpret-trailers.txt |  2 +-\n Documentation/git-ls-files.txt           |  2 +-\n Documentation/git-p4.txt                 | 20 +++++++++----------\n Documentation/git-push.txt               |  2 +-\n Documentation/git-rebase.txt             | 10 +++++-----\n Documentation/git-remote.txt             | 10 +++++-----\n Documentation/git-revert.txt             |  4 ++--\n Documentation/git-send-email.txt         | 24 +++++++++++-----------\n Documentation/git-send-pack.txt          | 10 +++++-----\n Documentation/git-show-branch.txt        |  2 +-\n Documentation/git-show-ref.txt           |  6 +++---\n Documentation/git-svn.txt                | 26 ++++++++++++------------\n Documentation/git-tag.txt                |  2 +-\n Documentation/git-update-index.txt       | 14 ++++++-------\n Documentation/git-web--browse.txt        |  2 +-\n Documentation/git.txt                    |  8 ++++----\n Documentation/gitcore-tutorial.txt       |  2 +-\n Documentation/gitdiffcore.txt            |  4 ++--\n Documentation/gitk.txt                   |  2 +-\n Documentation/gitmodules.txt             |  2 +-\n Documentation/gitremote-helpers.txt      |  8 ++++----\n Documentation/revisions.txt              |  2 +-\n 46 files changed, 150 insertions(+), 150 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex c483785..0903bf3 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -140,7 +140,7 @@ boolean::\n        false;; Boolean false can be spelled as `no`, `off`,\n \t\t`false`, or `0`.\n +\n-When converting value to the canonical form using '--bool' type\n+When converting value to the canonical form using `--bool` type\n specifier; 'git config' will ensure that the output is \"true\" or\n \"false\" (spelled in lowercase).\n \n@@ -481,7 +481,7 @@ core.worktree::\n \tIf `GIT_COMMON_DIR` environment variable is set, core.worktree\n \tis ignored and not used for determining the root of working tree.\n \tThis can be overridden by the `GIT_WORK_TREE` environment\n-\tvariable and the '--work-tree' command-line option.\n+\tvariable and the `--work-tree` command-line option.\n \tThe value can be an absolute path or relative to the path to\n \tthe .git directory, which is either specified by --git-dir\n \tor GIT_DIR, or automatically discovered.\n@@ -762,7 +762,7 @@ core.abbrev::\n add.ignoreErrors::\n add.ignore-errors (deprecated)::\n \tTells 'git add' to continue adding files when some files cannot be\n-\tadded due to indexing errors. Equivalent to the '--ignore-errors'\n+\tadded due to indexing errors. Equivalent to the `--ignore-errors`\n \toption of linkgit:git-add[1].  `add.ignore-errors` is deprecated,\n \tas it does not follow the usual naming convention for configuration\n \tvariables.\n@@ -788,9 +788,9 @@ from the original current directory. See linkgit:git-rev-parse[1].\n \n am.keepcr::\n \tIf true, git-am will call git-mailsplit for patches in mbox format\n-\twith parameter '--keep-cr'. In this case git-mailsplit will\n+\twith parameter `--keep-cr`. In this case git-mailsplit will\n \tnot remove `\\r` from lines ending with `\\r\\n`. Can be overridden\n-\tby giving '--no-keep-cr' from the command line.\n+\tby giving `--no-keep-cr` from the command line.\n \tSee linkgit:git-am[1], linkgit:git-mailsplit[1].\n \n am.threeWay::\n@@ -803,7 +803,7 @@ am.threeWay::\n \n apply.ignoreWhitespace::\n \tWhen set to 'change', tells 'git apply' to ignore changes in\n-\twhitespace, in the same way as the '--ignore-space-change'\n+\twhitespace, in the same way as the `--ignore-space-change`\n \toption.\n \tWhen set to one of: no, none, never, false tells 'git apply' to\n \trespect all whitespace differences.\n@@ -811,7 +811,7 @@ apply.ignoreWhitespace::\n \n apply.whitespace::\n \tTells 'git apply' how to handle whitespaces, in the same way\n-\tas the '--whitespace' option. See linkgit:git-apply[1].\n+\tas the `--whitespace` option. See linkgit:git-apply[1].\n \n branch.autoSetupMerge::\n \tTells 'git branch' and 'git checkout' to set up new branches\n@@ -1470,13 +1470,13 @@ grep.lineNumber::\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\n-\t'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',\n-\t'--fixed-strings', or '--perl-regexp' option accordingly, while the\n+\t'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,\n+\t`--fixed-strings`, or `--perl-regexp` option accordingly, while the\n \tvalue 'default' will return to the default matching behavior.\n \n grep.extendedRegexp::\n-\tIf set to true, enable '--extended-regexp' option by default. This\n-\toption is ignored when the `grep.patternType` option is set to a value\n+\tIf set to true, enable `--extended-regexp` option by default. This\n+\toption is ignored when the 'grep.patternType' option is set to a value\n \tother than 'default'.\n \n grep.threads::\n@@ -1916,7 +1916,7 @@ log.decorate::\n \tcommand. If 'short' is specified, the ref name prefixes 'refs/heads/',\n \t'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is\n \tspecified, the full ref name (including prefix) will be printed.\n-\tThis is the same as the log commands '--decorate' option.\n+\tThis is the same as the log commands `--decorate` option.\n \n log.follow::\n \tIf `true`, `git log` will act as if the `--follow` option was used when\n@@ -2298,16 +2298,16 @@ new default).\n --\n \n push.followTags::\n-\tIf set to true enable '--follow-tags' option by default.  You\n+\tIf set to true enable `--follow-tags` option by default.  You\n \tmay override this configuration at time of push by specifying\n-\t'--no-follow-tags'.\n+\t`--no-follow-tags`.\n \n push.gpgSign::\n \tMay be set to a boolean value, or the string 'if-asked'. A true\n-\tvalue causes all pushes to be GPG signed, as if '--signed' is\n+\tvalue causes all pushes to be GPG signed, as if `--signed` is\n \tpassed to linkgit:git-push[1]. The string 'if-asked' causes\n \tpushes to be signed if the server supports it, as if\n-\t'--signed=if-asked' is passed to 'git push'. A false value may\n+\t`--signed=if-asked` is passed to 'git push'. A false value may\n \toverride a value from a lower-priority config file. An explicit\n \tcommand-line flag always overrides this config option.\n \n@@ -2330,7 +2330,7 @@ rebase.stat::\n \trebase. False by default.\n \n rebase.autoSquash::\n-\tIf set to true enable '--autosquash' option by default.\n+\tIf set to true enable `--autosquash` option by default.\n \n rebase.autoStash::\n \tWhen set to true, automatically create a temporary stash\ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\nindex f10fd54..cf52626 100644\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -86,7 +86,7 @@ diff format for merges\n ----------------------\n \n \"git-diff-tree\", \"git-diff-files\" and \"git-diff --raw\"\n-can take `-c` or '--cc' option\n+can take `-c` or `--cc` option\n to generate diff output also for merge commits.  The output differs\n from the format described above in the following way:\n \ndiff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt\nindex 18608f5..d2a7ff5 100644\n--- a/Documentation/diff-generate-patch.txt\n+++ b/Documentation/diff-generate-patch.txt\n@@ -2,7 +2,7 @@ Generating patches with -p\n --------------------------\n \n When \"git-diff-index\", \"git-diff-tree\", or \"git-diff-files\" are run\n-with a `-p` option, \"git diff\" without the '--raw' option, or\n+with a `-p` option, \"git diff\" without the `--raw` option, or\n \"git log\" with the \"-p\" option, they\n do not produce the output described above; instead they produce a\n patch file.  You can customize the creation of such patches via the\n@@ -118,7 +118,7 @@ index fabadb8,cc95eb0..4866510\n \n        diff --combined file\n +\n-or like this (when '--cc' option is used):\n+or like this (when `--cc` option is used):\n \n        diff --cc file\n \ndiff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt\nindex 036edfb..dcc68b9 100644\n--- a/Documentation/fetch-options.txt\n+++ b/Documentation/fetch-options.txt\n@@ -88,7 +88,7 @@ ifndef::git-pull[]\n \tto whatever else would otherwise be fetched.  Using this\n \toption alone does not subject tags to pruning, even if --prune\n \tis used (though tags may be pruned anyway if they are also the\n-\tdestination of an explicit refspec; see '--prune').\n+\tdestination of an explicit refspec; see `--prune`).\n \n --recurse-submodules[=yes|on-demand|no]::\n \tThis option controls if and under what conditions new commits of\n@@ -110,7 +110,7 @@ ifndef::git-pull[]\n \n --no-recurse-submodules::\n \tDisable recursive fetching of submodules (this has the same effect as\n-\tusing the '--recurse-submodules=no' option).\n+\tusing the `--recurse-submodules=no` option).\n \n --submodule-prefix=<path>::\n \tPrepend <path> to paths printed in informative messages\n@@ -137,7 +137,7 @@ endif::git-pull[]\n \n --upload-pack <upload-pack>::\n \tWhen given, and the repository to fetch from is handled\n-\tby 'git fetch-pack', '--exec=<upload-pack>' is passed to\n+\tby 'git fetch-pack', `--exec=<upload-pack>` is passed to\n \tthe command to specify non-default path for the command\n \trun on the other end.\n \ndiff --git a/Documentation/git-am.txt b/Documentation/git-am.txt\nindex 13cdd7f..8dd9e4f 100644\n--- a/Documentation/git-am.txt\n+++ b/Documentation/git-am.txt\n@@ -198,12 +198,12 @@ When initially invoking `git am`, you give it the names of the mailboxes\n to process.  Upon seeing the first patch that does not apply, it\n aborts in the middle.  You can recover from this in one of two ways:\n \n-. skip the current patch by re-running the command with the '--skip'\n+. skip the current patch by re-running the command with the `--skip`\n   option.\n \n . hand resolve the conflict in the working directory, and update\n   the index file to bring it into a state that the patch should\n-  have produced.  Then run the command with the '--continue' option.\n+  have produced.  Then run the command with the `--continue` option.\n \n The command refuses to process new mailboxes until the current\n operation is finished, so if you decide to start over from scratch,\ndiff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt\nindex 4a7037f..123144f 100644\n--- a/Documentation/git-branch.txt\n+++ b/Documentation/git-branch.txt\n@@ -172,7 +172,7 @@ This option is only applicable in non-verbose mode.\n +\n This behavior is the default when the start point is a remote-tracking branch.\n Set the branch.autoSetupMerge configuration variable to `false` if you\n-want `git checkout` and `git branch` to always behave as if '--no-track'\n+want `git checkout` and `git branch` to always behave as if `--no-track`\n were given. Set it to `always` if you want this behavior when the\n start-point is either a local or remote-tracking branch.\n \ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex f8d0dcf..18d03d8 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -16,7 +16,7 @@ DESCRIPTION\n -----------\n In its first form, the command provides the content or the type of an object in\n the repository. The type is required unless `-t` or `-p` is used to find the\n-object type, or `-s` is used to find the object size, or '--textconv' is used\n+object type, or `-s` is used to find the object size, or `--textconv` is used\n (which implies type \"blob\").\n \n In the second form, a list of objects (separated by linefeeds) is provided on\ndiff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt\nindex 6154e57..c95b715 100644\n--- a/Documentation/git-cherry-pick.txt\n+++ b/Documentation/git-cherry-pick.txt\n@@ -47,7 +47,7 @@ OPTIONS\n \tFor a more complete list of ways to spell commits, see\n \tlinkgit:gitrevisions[7].\n \tSets of commits can be passed but no traversal is done by\n-\tdefault, as if the '--no-walk' option was specified, see\n+\tdefault, as if the `--no-walk` option was specified, see\n \tlinkgit:git-rev-list[1]. Note that specifying a range will\n \tfeed all <commit>... arguments to a single revision walk\n \t(see a later example that uses 'maint master..next').\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex 2afda81..448f42c 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -260,7 +260,7 @@ FROM UPSTREAM REBASE\" section in linkgit:git-rebase[1].)\n \tstaged for other paths. This is the default mode of operation of\n \t'git commit' if any paths are given on the command line,\n \tin which case this option can be omitted.\n-\tIf this option is specified together with '--amend', then\n+\tIf this option is specified together with `--amend`, then\n \tno paths need to be specified, which can be used to amend\n \tthe last commit without committing changes that have\n \talready been staged.\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex a89c304..79905fb 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -31,29 +31,29 @@ You can query/set/replace/unset options with this command. The name is\n actually the section and the key separated by a dot, and the value will be\n escaped.\n \n-Multiple lines can be added to an option by using the '--add' option.\n+Multiple lines can be added to an option by using the `--add` option.\n If you want to update or unset an option which can occur on multiple\n lines, a POSIX regexp `value_regex` needs to be given.  Only the\n existing values that match the regexp are updated or unset.  If\n you want to handle the lines that do *not* match the regex, just\n prepend a single exclamation mark in front (see also <<EXAMPLES>>).\n \n-The type specifier can be either '--int' or '--bool', to make\n+The type specifier can be either `--int` or `--bool`, to make\n 'git config' ensure that the variable(s) are of the given type and\n convert the value to the canonical form (simple decimal number for int,\n-a \"true\" or \"false\" string for bool), or '--path', which does some\n-path expansion (see '--path' below).  If no type specifier is passed, no\n+a \"true\" or \"false\" string for bool), or `--path`, which does some\n+path expansion (see `--path` below).  If no type specifier is passed, no\n checks or transformations are performed on the value.\n \n When reading, the values are read from the system, global and\n repository local configuration files by default, and options\n-'--system', '--global', '--local' and '--file <filename>' can be\n+`--system`, `--global`, `--local` and '--file <filename>' can be\n used to tell the command to read from only that location (see <<FILES>>).\n \n When writing, the new value is written to the repository local\n-configuration file by default, and options '--system', '--global',\n+configuration file by default, and options `--system`, `--global`,\n '--file <filename>' can be used to tell the command to write to\n-that location (you can say '--local' but that is the default).\n+that location (you can say `--local` but that is the default).\n \n This command will fail with non-zero status upon error.  Some exit\n codes are:\n@@ -138,7 +138,7 @@ See also <<FILES>>.\n \tUse the given config file instead of the one specified by GIT_CONFIG.\n \n --blob blob::\n-\tSimilar to '--file' but use the given blob instead of a file. E.g.\n+\tSimilar to `--file` but use the given blob instead of a file. E.g.\n \tyou can use 'master:.gitmodules' to read values from the file\n \t'.gitmodules' in the master branch. See \"SPECIFYING REVISIONS\"\n \tsection in linkgit:gitrevisions[7] for a more complete list of\n@@ -220,7 +220,7 @@ See also <<FILES>>.\n -e::\n --edit::\n \tOpens an editor to modify the specified config file; either\n-\t'--system', '--global', or repository (default).\n+\t`--system`, `--global`, or repository (default).\n \n --[no-]includes::\n \tRespect `include.*` directives in config files when looking up\n@@ -232,7 +232,7 @@ See also <<FILES>>.\n FILES\n -----\n \n-If not set explicitly with '--file', there are four files where\n+If not set explicitly with `--file`, there are four files where\n 'git config' will search for configuration options:\n \n $(prefix)/etc/gitconfig::\n@@ -264,11 +264,11 @@ precedence over values read earlier.  When multiple values are taken then all\n values of a key from all files will be used.\n \n All writing options will per default write to the repository specific\n-configuration file. Note that this also affects options like '--replace-all'\n-and '--unset'. *'git config' will only ever change one file at a time*.\n+configuration file. Note that this also affects options like `--replace-all`\n+and `--unset`. *'git config' will only ever change one file at a time*.\n \n You can override these rules either by command-line options or by environment\n-variables. The '--global' and the '--system' options will limit the file used\n+variables. The `--global` and the `--system` options will limit the file used\n to the global or system-wide file respectively. The `GIT_CONFIG` environment\n variable has a similar effect, but you can specify any filename you want.\n \ndiff --git a/Documentation/git-credential-store.txt b/Documentation/git-credential-store.txt\nindex e3c8f27..25fb963 100644\n--- a/Documentation/git-credential-store.txt\n+++ b/Documentation/git-credential-store.txt\n@@ -44,7 +44,7 @@ OPTIONS\n FILES\n -----\n \n-If not set explicitly with '--file', there are two files where\n+If not set explicitly with `--file`, there are two files where\n git-credential-store will search for credentials in order of precedence:\n \n ~/.git-credentials::\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex 5e3c6a8..a1a5234 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -54,7 +54,7 @@ Print usage information and exit\n You can specify a list of allowed directories. If no directories\n are given, all are allowed. This is an additional restriction, gitcvs\n access still needs to be enabled by the `gitcvs.enabled` config option\n-unless '--export-all' was given, too.\n+unless `--export-all` was given, too.\n \n \n DESCRIPTION\ndiff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt\nindex dc20275..7901c54 100644\n--- a/Documentation/git-daemon.txt\n+++ b/Documentation/git-daemon.txt\n@@ -30,7 +30,7 @@ that service if it is enabled.\n \n It verifies that the directory has the magic file \"git-daemon-export-ok\", and\n it will refuse to export any Git directory that hasn't explicitly been marked\n-for export this way (unless the '--export-all' parameter is specified). If you\n+for export this way (unless the `--export-all` parameter is specified). If you\n pass some directory paths as 'git daemon' arguments, you can further restrict\n the offers to a whitelist comprising of those.\n \n@@ -90,10 +90,10 @@ OPTIONS\n \tis not supported, then --listen=hostname is also not supported and\n \t--listen must be given an IPv4 address.\n \tCan be given more than once.\n-\tIncompatible with '--inetd' option.\n+\tIncompatible with `--inetd` option.\n \n --port=<n>::\n-\tListen on an alternative port.  Incompatible with '--inetd' option.\n+\tListen on an alternative port.  Incompatible with `--inetd` option.\n \n --init-timeout=<n>::\n \tTimeout (in seconds) between the moment the connection is established\ndiff --git a/Documentation/git-describe.txt b/Documentation/git-describe.txt\nindex c8f28c8..e4ac448 100644\n--- a/Documentation/git-describe.txt\n+++ b/Documentation/git-describe.txt\n@@ -154,7 +154,7 @@ is found, its name will be output and searching will stop.\n If an exact match was not found, 'git describe' will walk back\n through the commit history to locate an ancestor commit which\n has been tagged.  The ancestor's tag will be output along with an\n-abbreviation of the input commit-ish's SHA-1. If '--first-parent' was\n+abbreviation of the input commit-ish's SHA-1. If `--first-parent` was\n specified then the walk will only consider the first parent of each\n commit.\n \ndiff --git a/Documentation/git-diff-index.txt b/Documentation/git-diff-index.txt\nindex a86cf62..a171506 100644\n--- a/Documentation/git-diff-index.txt\n+++ b/Documentation/git-diff-index.txt\n@@ -40,13 +40,13 @@ include::diff-format.txt[]\n Operating Modes\n ---------------\n You can choose whether you want to trust the index file entirely\n-(using the '--cached' flag) or ask the diff logic to show any files\n+(using the `--cached` flag) or ask the diff logic to show any files\n that don't match the stat state as being \"tentatively changed\".  Both\n of these operations are very useful indeed.\n \n Cached Mode\n -----------\n-If '--cached' is specified, it allows you to ask:\n+If `--cached` is specified, it allows you to ask:\n \n \tshow me the differences between HEAD and the current index\n \tcontents (the ones I'd write using 'git write-tree')\ndiff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt\nindex 7558e49..7870e17 100644\n--- a/Documentation/git-diff-tree.txt\n+++ b/Documentation/git-diff-tree.txt\n@@ -43,11 +43,11 @@ include::diff-options.txt[]\n \tshow tree entry itself as well as subtrees.  Implies -r.\n \n --root::\n-\tWhen '--root' is specified the initial commit will be shown as a big\n+\tWhen `--root` is specified the initial commit will be shown as a big\n \tcreation event. This is equivalent to a diff against the NULL tree.\n \n --stdin::\n-\tWhen '--stdin' is specified, the command does not take\n+\tWhen `--stdin` is specified, the command does not take\n \t<tree-ish> arguments from the command line.  Instead, it\n \treads lines containing either two <tree>, one <commit>, or a\n \tlist of <commit> from its standard input.  (Use a single space\n@@ -91,7 +91,7 @@ include::pretty-options.txt[]\n -c::\n \tThis flag changes the way a merge commit is displayed\n \t(which means it is useful only when the command is given\n-\tone <tree-ish>, or '--stdin').  It shows the differences\n+\tone <tree-ish>, or `--stdin`).  It shows the differences\n \tfrom each of the parents to the merge result simultaneously\n \tinstead of showing pairwise diff between a parent and the\n \tresult one at a time (which is what the `-m` option does).\ndiff --git a/Documentation/git-difftool.txt b/Documentation/git-difftool.txt\nindex 333cf6f..224fb30 100644\n--- a/Documentation/git-difftool.txt\n+++ b/Documentation/git-difftool.txt\n@@ -98,7 +98,7 @@ instead.  `--no-symlinks` is the default on Windows.\n \tinvoked diff tool returns a non-zero exit code.\n +\n 'git-difftool' will forward the exit code of the invoked tool when\n-'--trust-exit-code' is used.\n+`--trust-exit-code` is used.\n \n See linkgit:git-diff[1] for the full list of supported options.\n \ndiff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt\nindex 4c8219d..24417ee 100644\n--- a/Documentation/git-fetch-pack.txt\n+++ b/Documentation/git-fetch-pack.txt\n@@ -41,7 +41,7 @@ OPTIONS\n \toption, then the refs from stdin are processed after those\n \ton the command line.\n +\n-If '--stateless-rpc' is specified together with this option then\n+If `--stateless-rpc` is specified together with this option then\n the list of refs must be in packet format (pkt-line). Each ref must\n be in a separate packet, and the list must end with a flush packet.\n \ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex 2d30297..060ebb3 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -171,7 +171,7 @@ to other tags will be rewritten to point to the underlying commit.\n \tuntouched.  This switch allow git-filter-branch to ignore such\n \tcommits.  Though, this switch only applies for commits that have one\n \tand only one parent, it will hence keep merges points. Also, this\n-\toption is not compatible with the use of '--commit-filter'. Though you\n+\toption is not compatible with the use of `--commit-filter`. Though you\n \tjust need to use the function 'git_commit_non_empty_tree \"$@\"' instead\n \tof the `git commit-tree \"$@\"` idiom in your commit filter to make that\n \thappen.\n@@ -197,7 +197,7 @@ to other tags will be rewritten to point to the underlying commit.\n <rev-list options>...::\n \tArguments for 'git rev-list'.  All positive refs included by\n \tthese options are rewritten.  You may also specify options\n-\tsuch as '--all', but you must use '--' to separate them from\n+\tsuch as `--all`, but you must use '--' to separate them from\n \tthe 'git filter-branch' options. Implies <<Remap_to_ancestor>>.\n \n \ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex d9d406d..f57e69b 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -142,7 +142,7 @@ align::\n \t<width> and <position> used instead.  For instance,\n \t`%(align:<width>,<position>)`. If the contents length is more\n \tthan the width then no alignment is performed. If used with\n-\t'--quote' everything in between %(align:...) and %(end) is\n+\t`--quote` everything in between %(align:...) and %(end) is\n \tquoted, but if nested then only the topmost level performs\n \tquoting.\n \ndiff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt\nindex 84ee92e..7fc68eb 100644\n--- a/Documentation/git-fsck.txt\n+++ b/Documentation/git-fsck.txt\n@@ -95,7 +95,7 @@ DISCUSSION\n git-fsck tests SHA-1 and general object sanity, and it does full tracking\n of the resulting reachability and everything else. It prints out any\n corruption it finds (missing or bad objects), and if you use the\n-'--unreachable' flag it will also print out objects that exist but that\n+`--unreachable` flag it will also print out objects that exist but that\n aren't reachable from any of the specified head nodes (or the default\n set, as mentioned above).\n \ndiff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt\nindex 557973b..0ecea6e 100644\n--- a/Documentation/git-grep.txt\n+++ b/Documentation/git-grep.txt\n@@ -45,12 +45,12 @@ grep.lineNumber::\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\n-\t'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',\n-\t'--fixed-strings', or '--perl-regexp' option accordingly, while the\n+\t'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,\n+\t`--fixed-strings`, or `--perl-regexp` option accordingly, while the\n \tvalue 'default' will return to the default matching behavior.\n \n grep.extendedRegexp::\n-\tIf set to true, enable '--extended-regexp' option by default. This\n+\tIf set to true, enable `--extended-regexp` option by default. This\n \toption is ignored when the `grep.patternType` option is set to a value\n \tother than 'default'.\n \n@@ -59,7 +59,7 @@ grep.threads::\n \t8 threads are used by default (for now).\n \n grep.fullName::\n-\tIf set to true, enable '--full-name' option by default.\n+\tIf set to true, enable `--full-name` option by default.\n \n grep.fallbackToNoIndex::\n \tIf set to true, fall back to git grep --no-index if git grep\ndiff --git a/Documentation/git-help.txt b/Documentation/git-help.txt\nindex c6f7ce7..40d328a 100644\n--- a/Documentation/git-help.txt\n+++ b/Documentation/git-help.txt\n@@ -18,10 +18,10 @@ With no options and no COMMAND or GUIDE given, the synopsis of the 'git'\n command and a list of the most commonly used Git commands are printed\n on the standard output.\n \n-If the option '--all' or `-a` is given, all available commands are\n+If the option `--all` or `-a` is given, all available commands are\n printed on the standard output.\n \n-If the option '--guide' or `-g` is given, a list of the useful\n+If the option `--guide` or `-g` is given, a list of the useful\n Git guides is also printed on the standard output.\n \n If a command, or a guide, is given, a manual page for that command or\n@@ -176,7 +176,7 @@ Note about git config --global\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n Note that all these configuration variables should probably be set\n-using the '--global' flag, for example like this:\n+using the `--global` flag, for example like this:\n \n ------------------------------------------------\n $ git config --global help.format web\ndiff --git a/Documentation/git-http-push.txt b/Documentation/git-http-push.txt\nindex 2e67362..2aceb6f 100644\n--- a/Documentation/git-http-push.txt\n+++ b/Documentation/git-http-push.txt\n@@ -81,13 +81,13 @@ destination side.\n      exist in the set of remote refs; the ref matched <src>\n      locally is used as the name of the destination.\n \n-Without '--force', the <src> ref is stored at the remote only if\n+Without `--force`, the <src> ref is stored at the remote only if\n <dst> does not exist, or <dst> is a proper subset (i.e. an\n ancestor) of <src>.  This check, known as \"fast-forward check\",\n is performed in order to avoid accidentally overwriting the\n remote ref and lose other peoples' commits from there.\n \n-With '--force', the fast-forward check is disabled for all refs.\n+With `--force`, the fast-forward check is disabled for all refs.\n \n Optionally, a <ref> parameter can be prefixed with a plus '+' sign\n to disable the fast-forward check only on that ref.\ndiff --git a/Documentation/git-interpret-trailers.txt b/Documentation/git-interpret-trailers.txt\nindex a77b901..93d1db6 100644\n--- a/Documentation/git-interpret-trailers.txt\n+++ b/Documentation/git-interpret-trailers.txt\n@@ -219,7 +219,7 @@ Signed-off-by: Alice <alice@example.com>\n Signed-off-by: Bob <bob@example.com>\n ------------\n \n-* Use the '--in-place' option to edit a message file in place:\n+* Use the `--in-place` option to edit a message file in place:\n +\n ------------\n $ cat msg.txt\ndiff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt\nindex 75c3f41..078b556 100644\n--- a/Documentation/git-ls-files.txt\n+++ b/Documentation/git-ls-files.txt\n@@ -175,7 +175,7 @@ followed by the  (\"attr/<eolattr>\").\n \n Output\n ------\n-'git ls-files' just outputs the filenames unless '--stage' is specified in\n+'git ls-files' just outputs the filenames unless `--stage` is specified in\n which case it outputs:\n \n         [<tag> ]<mode> <object> <stage> <file>\ndiff --git a/Documentation/git-p4.txt b/Documentation/git-p4.txt\nindex 454bdb3..2703648 100644\n--- a/Documentation/git-p4.txt\n+++ b/Documentation/git-p4.txt\n@@ -104,7 +104,7 @@ $ git p4 sync //path/in/your/perforce/depot\n ------------\n This imports the specified depot into\n 'refs/remotes/p4/master' in an existing Git repository.  The\n-'--branch' option can be used to specify a different branch to\n+`--branch` option can be used to specify a different branch to\n be used for the p4 content.\n \n If a Git repository includes branches 'refs/remotes/origin/p4', these\n@@ -114,7 +114,7 @@ from a Git remote, this can be useful in a multi-developer environment.\n \n If there are multiple branches, doing 'git p4 sync' will automatically\n use the \"BRANCH DETECTION\" algorithm to try to partition new changes\n-into the right branch.  This can be overridden with the '--branch'\n+into the right branch.  This can be overridden with the `--branch`\n option to specify just a single branch to update.\n \n \n@@ -150,10 +150,10 @@ $ git p4 submit topicbranch\n ------------\n \n The upstream reference is generally 'refs/remotes/p4/master', but can\n-be overridden using the '--origin=' command-line option.\n+be overridden using the `--origin=` command-line option.\n \n The p4 changes will be created as the user invoking 'git p4 submit'. The\n-'--preserve-user' option will cause ownership to be modified\n+`--preserve-user` option will cause ownership to be modified\n according to the author of the Git commit.  This option requires admin\n privileges in p4, which can be granted using 'p4 protect'.\n \n@@ -221,7 +221,7 @@ Git repository:\n \twhere they will be treated as remote-tracking branches by\n \tlinkgit:git-branch[1] and other commands.  This option instead\n \tputs p4 branches in 'refs/heads/p4/'.  Note that future\n-\tsync operations must specify '--import-local' as well so that\n+\tsync operations must specify `--import-local` as well so that\n \tthey can find the p4 branches in refs/heads.\n \n --max-changes <n>::\n@@ -245,7 +245,7 @@ Git repository:\n \tdefault, involves removing the entire depot path.  With this\n \toption, the full p4 depot path is retained in Git.  For example,\n \tpath '//depot/main/foo/bar.c', when imported from\n-\t'//depot/main/', becomes 'foo/bar.c'.  With '--keep-path', the\n+\t'//depot/main/', becomes 'foo/bar.c'.  With `--keep-path`, the\n \tGit path is instead 'depot/main/foo/bar.c'.\n \n --use-client-spec::\n@@ -341,7 +341,7 @@ p4 revision specifier on the end:\n     Import all changes from both named depot paths into a single\n     repository.  Only files below these directories are included.\n     There is not a subdirectory in Git for each \"proj1\" and \"proj2\".\n-    You must use the '--destination' option when specifying more\n+    You must use the `--destination` option when specifying more\n     than one depot path.  The revision specifier must be specified\n     identically on each depot path.  If there are files in the\n     depot paths with the same name, the path with the most recently\n@@ -355,7 +355,7 @@ CLIENT SPEC\n The p4 client specification is maintained with the 'p4 client' command\n and contains among other fields, a View that specifies how the depot\n is mapped into the client repository.  The 'clone' and 'sync' commands\n-can consult the client spec when given the '--use-client-spec' option or\n+can consult the client spec when given the `--use-client-spec` option or\n when the useClientSpec variable is true.  After 'git p4 clone', the\n useClientSpec variable is automatically set in the repository\n configuration file.  This allows future 'git p4 submit' commands to\n@@ -390,7 +390,7 @@ different areas in the tree, and indicate related content.  'git p4'\n can use these mappings to determine branch relationships.\n \n If you have a repository where all the branches of interest exist as\n-subdirectories of a single depot path, you can use '--detect-branches'\n+subdirectories of a single depot path, you can use `--detect-branches`\n when cloning or syncing to have 'git p4' automatically find\n subdirectories in p4, and to generate these as branches in Git.\n \n@@ -507,7 +507,7 @@ git-p4.labelImportRegexp::\n git-p4.useClientSpec::\n \tSpecify that the p4 client spec should be used to identify p4\n \tdepot paths of interest.  This is equivalent to specifying the\n-\toption '--use-client-spec'.  See the \"CLIENT SPEC\" section above.\n+\toption `--use-client-spec`.  See the \"CLIENT SPEC\" section above.\n \tThis variable is a boolean, not the name of a p4 client.\n \n git-p4.pathEncoding::\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 19f46b6..93c3527 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -275,7 +275,7 @@ origin +master` to force a push to the `master` branch). See the\n \tall submodules that changed in the revisions to be pushed will be\n \tpushed. If on-demand was not able to push all necessary revisions\n \tit will also be aborted and exit with non-zero status. A value of\n-\t'no' or using '--no-recurse-submodules' can be used to override the\n+\t'no' or using `--no-recurse-submodules` can be used to override the\n \tpush.recurseSubmodules configuration variable when no submodule\n \trecursion is required.\n \ndiff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\nindex 6ed610a..a8078ff 100644\n--- a/Documentation/git-rebase.txt\n+++ b/Documentation/git-rebase.txt\n@@ -208,10 +208,10 @@ rebase.stat::\n \trebase. False by default.\n \n rebase.autoSquash::\n-\tIf set to true enable '--autosquash' option by default.\n+\tIf set to true enable `--autosquash` option by default.\n \n rebase.autoStash::\n-\tIf set to true enable '--autostash' option by default.\n+\tIf set to true enable `--autostash` option by default.\n \n rebase.missingCommitsCheck::\n \tIf set to \"warn\", print warnings about removed commits in\n@@ -220,7 +220,7 @@ rebase.missingCommitsCheck::\n \tdone. \"ignore\" by default.\n \n rebase.instructionFormat::\n-\tCustom commit list format to use during an '--interactive' rebase.\n+\tCustom commit list format to use during an `--interactive` rebase.\n \n OPTIONS\n -------\n@@ -428,9 +428,9 @@ squash/fixup series.\n \t\"fixup! \" or \"squash! \" after the first, in case you referred to an\n \tearlier fixup/squash with `git commit --fixup/--squash`.\n +\n-This option is only valid when the '--interactive' option is used.\n+This option is only valid when the `--interactive` option is used.\n +\n-If the '--autosquash' option is enabled by default using the\n+If the `--autosquash` option is enabled by default using the\n configuration variable `rebase.autoSquash`, this option can be\n used to override and disable this setting.\n \ndiff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt\nindex 1d7ecea..577b969 100644\n--- a/Documentation/git-remote.txt\n+++ b/Documentation/git-remote.txt\n@@ -137,9 +137,9 @@ branches, adds to that list.\n Retrieves the URLs for a remote. Configurations for `insteadOf` and\n `pushInsteadOf` are expanded here. By default, only the first URL is listed.\n +\n-With '--push', push URLs are queried rather than fetch URLs.\n+With `--push`, push URLs are queried rather than fetch URLs.\n +\n-With '--all', all URLs for the remote will be listed.\n+With `--all`, all URLs for the remote will be listed.\n \n 'set-url'::\n \n@@ -147,11 +147,11 @@ Changes URLs for the remote. Sets first URL for remote <name> that matches\n regex <oldurl> (first URL if no <oldurl> is given) to <newurl>. If\n <oldurl> doesn't match any URL, an error occurs and nothing is changed.\n +\n-With '--push', push URLs are manipulated instead of fetch URLs.\n+With `--push`, push URLs are manipulated instead of fetch URLs.\n +\n-With '--add', instead of changing existing URLs, new URL is added.\n+With `--add`, instead of changing existing URLs, new URL is added.\n +\n-With '--delete', instead of changing existing URLs, all URLs matching\n+With `--delete`, instead of changing existing URLs, all URLs matching\n regex <url> are deleted for remote <name>.  Trying to delete all\n non-push URLs is an error.\n +\ndiff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\nindex 573616a..837707a 100644\n--- a/Documentation/git-revert.txt\n+++ b/Documentation/git-revert.txt\n@@ -24,7 +24,7 @@ from the HEAD commit).\n Note: 'git revert' is used to record some new commits to reverse the\n effect of some earlier commits (often only a faulty one).  If you want to\n throw away all uncommitted changes in your working directory, you\n-should see linkgit:git-reset[1], particularly the '--hard' option.  If\n+should see linkgit:git-reset[1], particularly the `--hard` option.  If\n you want to extract specific files as they were in another commit, you\n should see linkgit:git-checkout[1], specifically the `git checkout\n <commit> -- <filename>` syntax.  Take care with these alternatives as\n@@ -37,7 +37,7 @@ OPTIONS\n \tFor a more complete list of ways to spell commit names, see\n \tlinkgit:gitrevisions[7].\n \tSets of commits can also be given but no traversal is done by\n-\tdefault, see linkgit:git-rev-list[1] and its '--no-walk'\n+\tdefault, see linkgit:git-rev-list[1] and its `--no-walk`\n \toption.\n \n -e::\ndiff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt\nindex 00bfc81..d85b878 100644\n--- a/Documentation/git-send-email.txt\n+++ b/Documentation/git-send-email.txt\n@@ -66,7 +66,7 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When '--compose' is used, git send-email will use the From, Subject, and\n+When `--compose` is used, git send-email will use the From, Subject, and\n In-Reply-To headers specified in the message. If the body of the message\n (what you type after the headers and a blank line) only contains blank\n (or Git: prefixed) lines, the summary won't be sent, but From, Subject,\n@@ -182,19 +182,19 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor '--smtp-auth'\n+is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used.\n \n --smtp-pass[=<password>]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n \targument is specified, then the empty string is used as\n \tthe password. Default is the value of `sendemail.smtpPass`,\n-\thowever '--smtp-pass' always overrides this value.\n+\thowever `--smtp-pass` always overrides this value.\n +\n Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n-'--smtp-user' or a `sendemail.smtpUser`), but no password has been\n-specified (with '--smtp-pass' or `sendemail.smtpPass`), then\n+`--smtp-user` or a `sendemail.smtpUser`), but no password has been\n+specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n a password is obtained using 'git-credential'.\n \n --smtp-server=<host>::\n@@ -240,7 +240,7 @@ must be used for each option.\n \n --smtp-user=<user>::\n \tUsername for SMTP-AUTH. Default is the value of `sendemail.smtpUser`;\n-\tif a username is not specified (with '--smtp-user' or `sendemail.smtpUser`),\n+\tif a username is not specified (with `--smtp-user` or `sendemail.smtpUser`),\n \tthen authentication is not attempted.\n \n --smtp-debug=0|1::\n@@ -364,8 +364,8 @@ have been specified, in which case default to 'compose'.\n \n --[no-]format-patch::\n \tWhen an argument may be understood either as a reference or as a file name,\n-\tchoose to understand it as a format-patch argument ('--format-patch')\n-\tor as a file name ('--no-format-patch'). By default, when such a conflict\n+\tchoose to understand it as a format-patch argument (`--format-patch`)\n+\tor as a file name (`--no-format-patch`). By default, when such a conflict\n \toccurs, git send-email will fail.\n \n --quiet::\n@@ -382,7 +382,7 @@ have been specified, in which case default to 'compose'.\n --\n +\n Default is the value of `sendemail.validate`; if this is not set,\n-default to '--validate'.\n+default to `--validate`.\n \n --force::\n \tSend emails even if safety checks would prevent it.\n@@ -428,13 +428,13 @@ sendmail;;\n \n sendemail.multiEdit::\n \tIf true (default), a single editor instance will be spawned to edit\n-\tfiles you have to edit (patches when '--annotate' is used, and the\n-\tsummary when '--compose' is used). If false, files will be edited one\n+\tfiles you have to edit (patches when `--annotate` is used, and the\n+\tsummary when `--compose` is used). If false, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n \tSets the default for whether to confirm before sending. Must be\n-\tone of 'always', 'never', 'cc', 'compose', or 'auto'. See '--confirm'\n+\tone of 'always', 'never', 'cc', 'compose', or 'auto'. See `--confirm`\n \tin the previous section for the meaning of these values.\n \n EXAMPLE\ndiff --git a/Documentation/git-send-pack.txt b/Documentation/git-send-pack.txt\nindex 6aa91e8..a831dd0 100644\n--- a/Documentation/git-send-pack.txt\n+++ b/Documentation/git-send-pack.txt\n@@ -44,7 +44,7 @@ OPTIONS\n \toption, then the refs from stdin are processed after those\n \ton the command line.\n +\n-If '--stateless-rpc' is specified together with this option then\n+If `--stateless-rpc` is specified together with this option then\n the list of refs must be in packet format (pkt-line). Each ref must\n be in a separate packet, and the list must end with a flush packet.\n \n@@ -99,11 +99,11 @@ Specifying the Refs\n There are three ways to specify which refs to update on the\n remote end.\n \n-With '--all' flag, all refs that exist locally are transferred to\n+With `--all` flag, all refs that exist locally are transferred to\n the remote side.  You cannot specify any '<ref>' if you use\n this flag.\n \n-Without '--all' and without any '<ref>', the heads that exist\n+Without `--all` and without any '<ref>', the heads that exist\n both on the local side and on the remote side are updated.\n \n When one or more '<ref>' are specified explicitly (whether on the\n@@ -134,13 +134,13 @@ name. See linkgit:git-rev-parse[1].\n      exist in the set of remote refs; the ref matched <src>\n      locally is used as the name of the destination.\n \n-Without '--force', the <src> ref is stored at the remote only if\n+Without `--force`, the <src> ref is stored at the remote only if\n <dst> does not exist, or <dst> is a proper subset (i.e. an\n ancestor) of <src>.  This check, known as \"fast-forward check\",\n is performed in order to avoid accidentally overwriting the\n remote ref and lose other peoples' commits from there.\n \n-With '--force', the fast-forward check is disabled for all refs.\n+With `--force`, the fast-forward check is disabled for all refs.\n \n Optionally, a <ref> parameter can be prefixed with a plus '+' sign\n to disable the fast-forward check only on that ref.\ndiff --git a/Documentation/git-show-branch.txt b/Documentation/git-show-branch.txt\nindex b91d4e5..7818e0f 100644\n--- a/Documentation/git-show-branch.txt\n+++ b/Documentation/git-show-branch.txt\n@@ -60,7 +60,7 @@ OPTIONS\n         are shown before their parents).\n \n --date-order::\n-\tThis option is similar to '--topo-order' in the sense that no\n+\tThis option is similar to `--topo-order` in the sense that no\n \tparent comes before all of its children, but otherwise commits\n \tare ordered according to their commit date.\n \ndiff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt\nindex 3a32451..c0aa871 100644\n--- a/Documentation/git-show-ref.txt\n+++ b/Documentation/git-show-ref.txt\n@@ -60,7 +60,7 @@ OPTIONS\n \n \tEnable stricter reference checking by requiring an exact ref path.\n \tAside from returning an error code of 1, it will also print an error\n-\tmessage if '--quiet' was not specified.\n+\tmessage if `--quiet` was not specified.\n \n --abbrev[=<n>]::\n \n@@ -70,7 +70,7 @@ OPTIONS\n -q::\n --quiet::\n \n-\tDo not print any results to stdout. When combined with '--verify' this\n+\tDo not print any results to stdout. When combined with `--verify` this\n \tcan be used to silently check if a reference exists.\n \n --exclude-existing[=<pattern>]::\n@@ -134,7 +134,7 @@ use:\n This will show \"refs/heads/master\" but also \"refs/remote/other-repo/master\",\n if such references exists.\n \n-When using the '--verify' flag, the command requires an exact path:\n+When using the `--verify` flag, the command requires an exact path:\n \n -----------------------------------------------------------------------------\n \tgit show-ref --verify refs/heads/master\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 90a7079..935d3c2 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -98,11 +98,11 @@ your Perl's Getopt::Long is < v2.37).\n --ignore-paths=<regex>;;\n \tWhen passed to 'init' or 'clone' this regular expression will\n \tbe preserved as a config key.  See 'fetch' for a description\n-\tof '--ignore-paths'.\n+\tof `--ignore-paths`.\n --include-paths=<regex>;;\n \tWhen passed to 'init' or 'clone' this regular expression will\n \tbe preserved as a config key.  See 'fetch' for a description\n-\tof '--include-paths'.\n+\tof `--include-paths`.\n --no-minimize-url;;\n \tWhen tracking multiple directories (using --stdlayout,\n \t--branches, or --tags options), git svn will attempt to connect\n@@ -110,7 +110,7 @@ your Perl's Getopt::Long is < v2.37).\n \trepository.  This default allows better tracking of history if\n \tentire projects are moved within a repository, but may cause\n \tissues on repositories where read access restrictions are in\n-\tplace.  Passing '--no-minimize-url' will allow git svn to\n+\tplace.  Passing `--no-minimize-url` will allow git svn to\n \taccept URLs as-is without attempting to connect to a higher\n \tlevel directory.  This option is off by default when only\n \tone URL/branch is tracked (it would do little good).\n@@ -141,7 +141,7 @@ the same local time zone.\n --ignore-paths=<regex>;;\n \tThis allows one to specify a Perl regular expression that will\n \tcause skipping of all matching paths from checkout from SVN.\n-\tThe '--ignore-paths' option should match for every 'fetch'\n+\tThe `--ignore-paths` option should match for every 'fetch'\n \t(including automatic fetches due to 'clone', 'dcommit',\n \t'rebase', etc) on a given repository.\n +\n@@ -170,10 +170,10 @@ Skip \"branches\" and \"tags\" of first level directories;;\n --include-paths=<regex>;;\n \tThis allows one to specify a Perl regular expression that will\n \tcause the inclusion of only matching paths from checkout from SVN.\n-\tThe '--include-paths' option should match for every 'fetch'\n+\tThe `--include-paths` option should match for every 'fetch'\n \t(including automatic fetches due to 'clone', 'dcommit',\n-\t'rebase', etc) on a given repository. '--ignore-paths' takes\n-\tprecedence over '--include-paths'.\n+\t'rebase', etc) on a given repository. `--ignore-paths` takes\n+\tprecedence over `--include-paths`.\n +\n [verse]\n config key: svn-remote.<name>.include-paths\n@@ -191,7 +191,7 @@ config key: svn-remote.<name>.include-paths\n \tor if a second argument is passed; it will create a directory\n \tand work within that.  It accepts all arguments that the\n \t'init' and 'fetch' commands accept; with the exception of\n-\t'--fetch-all' and '--parent'.  After a repository is cloned,\n+\t`--fetch-all` and `--parent`.  After a repository is cloned,\n \tthe 'fetch' command will be able to update revisions without\n \taffecting the working tree; and the 'rebase' command will be\n \table to update the working tree with the latest changes.\n@@ -216,7 +216,7 @@ it preserves linear history with 'git rebase' instead of\n 'git merge' for ease of dcommitting with 'git svn'.\n +\n This accepts all options that 'git svn fetch' and 'git rebase'\n-accept.  However, '--fetch-all' only fetches from the current\n+accept.  However, `--fetch-all` only fetches from the current\n [svn-remote], and not all [svn-remote] definitions.\n +\n Like 'git rebase'; this requires that the working tree be clean\n@@ -905,7 +905,7 @@ parent of the branch. However, it is possible that there is no suitable\n Git commit to serve as parent.  This will happen, among other reasons,\n if the SVN branch is a copy of a revision that was not fetched by 'git\n svn' (e.g. because it is an old revision that was skipped with\n-'--revision'), or if in SVN a directory was copied that is not tracked\n+`--revision`), or if in SVN a directory was copied that is not tracked\n by 'git svn' (such as a branch that is not tracked at all, or a\n subdirectory of a tracked branch). In these cases, 'git svn' will still\n create a Git branch, but instead of using an existing Git commit as the\n@@ -982,12 +982,12 @@ directories in the working copy.  While this is the easiest way to get a\n copy of a complete repository, for projects with many branches it will\n lead to a working copy many times larger than just the trunk. Thus for\n projects using the standard directory structure (trunk/branches/tags),\n-it is recommended to clone with option '--stdlayout'. If the project\n+it is recommended to clone with option `--stdlayout`. If the project\n uses a non-standard structure, and/or if branches and tags are not\n required, it is easiest to only clone one directory (typically trunk),\n without giving any repository layout options.  If the full history with\n-branches and tags is required, the options '--trunk' / '--branches' /\n-'--tags' must be used.\n+branches and tags is required, the options `--trunk` / `--branches` /\n+`--tags` must be used.\n \n When using multiple --branches or --tags, 'git svn' does not automatically\n handle name collisions (for example, if two branches from different paths have\ndiff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt\nindex 4b1c1b8..499df56 100644\n--- a/Documentation/git-tag.txt\n+++ b/Documentation/git-tag.txt\n@@ -167,7 +167,7 @@ This option is only applicable when listing tags without annotation lines.\n \n --[no-]merged [<commit>]::\n \tOnly list tags whose tips are reachable, or not reachable\n-\tif '--no-merged' is used, from the specified commit ('HEAD'\n+\tif `--no-merged` is used, from the specified commit ('HEAD'\n \tif not specified).\n \n CONFIGURATION\ndiff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt\nindex c6cbed1..7386c93 100644\n--- a/Documentation/git-update-index.txt\n+++ b/Documentation/git-update-index.txt\n@@ -102,7 +102,7 @@ thus, in case the assumed-untracked file is changed upstream,\n you will need to handle the situation manually.\n \n --really-refresh::\n-\tLike '--refresh', but checks stat information unconditionally,\n+\tLike `--refresh`, but checks stat information unconditionally,\n \twithout regard to the \"assume unchanged\" setting.\n \n --[no-]skip-worktree::\n@@ -211,7 +211,7 @@ will remove the intended effect of the option.\n \n Using --refresh\n ---------------\n-'--refresh' does not calculate a new sha1 file or bring the index\n+`--refresh` does not calculate a new sha1 file or bring the index\n up-to-date for mode/content changes. But what it *does* do is to\n \"re-match\" the stat information of a file with the index, so that you\n can refresh the index for a file that hasn't been changed but where\n@@ -222,7 +222,7 @@ up the stat index details with the proper files.\n \n Using --cacheinfo or --info-only\n --------------------------------\n-'--cacheinfo' is used to register a file that is not in the\n+`--cacheinfo` is used to register a file that is not in the\n current working directory.  This is useful for minimum-checkout\n merging.\n \n@@ -232,12 +232,12 @@ To pretend you have a file with mode and sha1 at path, say:\n $ git update-index --cacheinfo <mode>,<sha1>,<path>\n ----------------\n \n-'--info-only' is used to register files without placing them in the object\n+`--info-only` is used to register files without placing them in the object\n database.  This is useful for status-only repositories.\n \n-Both '--cacheinfo' and '--info-only' behave similarly: the index is updated\n-but the object database isn't.  '--cacheinfo' is useful when the object is\n-in the database but the file isn't available locally.  '--info-only' is\n+Both `--cacheinfo` and `--info-only` behave similarly: the index is updated\n+but the object database isn't.  `--cacheinfo` is useful when the object is\n+in the database but the file isn't available locally.  `--info-only` is\n useful when the file is available, but you do not wish to update the\n object database.\n \ndiff --git a/Documentation/git-web--browse.txt b/Documentation/git-web--browse.txt\nindex 7daa28f..2d6b09a 100644\n--- a/Documentation/git-web--browse.txt\n+++ b/Documentation/git-web--browse.txt\n@@ -110,7 +110,7 @@ Note about git-config --global\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n Note that these configuration variables should probably be set using\n-the '--global' flag, for example like this:\n+the `--global` flag, for example like this:\n \n ------------------------------------------------\n $ git config --global web.browser firefox\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex 24efc63..56d579b 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -508,7 +508,7 @@ OPTIONS\n \n --help::\n \tPrints the synopsis and a list of the most commonly used\n-\tcommands. If the option '--all' or `-a` is given then all\n+\tcommands. If the option `--all` or `-a` is given then all\n \tavailable commands are printed. If a Git command is named this\n \toption will bring up the manual page for that command.\n +\n@@ -850,16 +850,16 @@ Git so take care if using a foreign front-end.\n \tIf the `GIT_DIR` environment variable is set then it\n \tspecifies a path to use instead of the default `.git`\n \tfor the base of the repository.\n-\tThe '--git-dir' command-line option also sets this value.\n+\tThe `--git-dir` command-line option also sets this value.\n \n `GIT_WORK_TREE`::\n \tSet the path to the root of the working tree.\n-\tThis can also be controlled by the '--work-tree' command-line\n+\tThis can also be controlled by the `--work-tree` command-line\n \toption and the core.worktree configuration variable.\n \n `GIT_NAMESPACE`::\n \tSet the Git namespace; see linkgit:gitnamespaces[7] for details.\n-\tThe '--namespace' command-line option also sets this value.\n+\tThe `--namespace` command-line option also sets this value.\n \n `GIT_CEILING_DIRECTORIES`::\n \tThis should be a colon-separated list of absolute paths.  If\ndiff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\nindex 15b3bfa..4546fa0 100644\n--- a/Documentation/gitcore-tutorial.txt\n+++ b/Documentation/gitcore-tutorial.txt\n@@ -949,7 +949,7 @@ for details.\n [NOTE]\n If there were more commits on the 'master' branch after the merge, the\n merge commit itself would not be shown by 'git show-branch' by\n-default.  You would need to provide '--sparse' option to make the\n+default.  You would need to provide `--sparse` option to make the\n merge commit visible in this case.\n \n Now, let's pretend you are the one who did all the work in\ndiff --git a/Documentation/gitdiffcore.txt b/Documentation/gitdiffcore.txt\nindex c579593..08cf622 100644\n--- a/Documentation/gitdiffcore.txt\n+++ b/Documentation/gitdiffcore.txt\n@@ -28,8 +28,8 @@ The 'git diff-{asterisk}' family works by first comparing two sets of\n files:\n \n  - 'git diff-index' compares contents of a \"tree\" object and the\n-   working directory (when '--cached' flag is not used) or a\n-   \"tree\" object and the index file (when '--cached' flag is\n+   working directory (when `--cached` flag is not used) or a\n+   \"tree\" object and the index file (when `--cached` flag is\n    used);\n \n  - 'git diff-files' compares contents of the index file and the\ndiff --git a/Documentation/gitk.txt b/Documentation/gitk.txt\nindex 6ade002..a68d860 100644\n--- a/Documentation/gitk.txt\n+++ b/Documentation/gitk.txt\n@@ -82,7 +82,7 @@ linkgit:git-rev-list[1] for a complete list.\n \n --simplify-merges::\n \n-\tAdditional option to '--full-history' to remove some needless\n+\tAdditional option to `--full-history` to remove some needless\n \tmerges from the resulting history, as there are no selected\n \tcommits contributing to this merge.  (See \"History\n \tsimplification\" in linkgit:git-log[1] for a more detailed\ndiff --git a/Documentation/gitmodules.txt b/Documentation/gitmodules.txt\nindex ac70eca..07cdd73 100644\n--- a/Documentation/gitmodules.txt\n+++ b/Documentation/gitmodules.txt\n@@ -19,7 +19,7 @@ of linkgit:git-config[1].\n \n The file contains one subsection per submodule, and the subsection value\n is the name of the submodule. The name is set to the path where the\n-submodule has been added unless it was customized with the '--name'\n+submodule has been added unless it was customized with the `--name`\n option of 'git submodule add'. Each submodule section also contains the\n following required keys:\n \ndiff --git a/Documentation/gitremote-helpers.txt b/Documentation/gitremote-helpers.txt\nindex 1e86594..53ce1d0 100644\n--- a/Documentation/gitremote-helpers.txt\n+++ b/Documentation/gitremote-helpers.txt\n@@ -210,17 +210,17 @@ the remote repository.\n 'export-marks' <file>::\n \tThis modifies the 'export' capability, instructing Git to dump the\n \tinternal marks table to <file> when complete. For details,\n-\tread up on '--export-marks=<file>' in linkgit:git-fast-export[1].\n+\tread up on `--export-marks=<file>` in linkgit:git-fast-export[1].\n \n 'import-marks' <file>::\n \tThis modifies the 'export' capability, instructing Git to load the\n \tmarks specified in <file> before processing any input. For details,\n-\tread up on '--import-marks=<file>' in linkgit:git-fast-export[1].\n+\tread up on `--import-marks=<file>` in linkgit:git-fast-export[1].\n \n 'signed-tags'::\n \tThis modifies the 'export' capability, instructing Git to pass\n-\t'--signed-tags=verbatim' to linkgit:git-fast-export[1].  In the\n-\tabsence of this capability, Git will use '--signed-tags=warn-strip'.\n+\t`--signed-tags=verbatim` to linkgit:git-fast-export[1].  In the\n+\tabsence of this capability, Git will use `--signed-tags=warn-strip`.\n \n \n \ndiff --git a/Documentation/revisions.txt b/Documentation/revisions.txt\nindex 19314e3..15879b3 100644\n--- a/Documentation/revisions.txt\n+++ b/Documentation/revisions.txt\n@@ -71,7 +71,7 @@ some output processing may assume ref names in UTF-8.\n   existing log ('$GIT_DIR/logs/<ref>'). Note that this looks up the state\n   of your *local* ref at a given time; e.g., what was in your local\n   'master' branch last week. If you want to look at commits made during\n-  certain times, see '--since' and '--until'.\n+  certain times, see `--since` and `--until`.\n \n '<refname>@{<n>}', e.g. 'master@\\{1\\}'::\n   A ref followed by the suffix '@' with an ordinal specification\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290311","messageId":"20160627185715.GB9594@sigill.intra.peff.net","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"Re: [PATCH 1/6] doc: typeset short command-line options as literal","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-27T18:57:15Z","receivedAt":"2016-06-27T18:57:23Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Jun 27, 2016 at 07:46:18PM +0200, Matthieu Moy wrote:\n\n> It was common in our documentation to surround short option names with\n> forward quotes, which renders as italic in HTML. Instead, use backquotes\n> which renders as monospace. This is one more step toward conformance to\n> Documentation/CodingGuidelines.\n> \n> This was obtained with:\n> \n>   perl -pi -e \"s/'(-[a-z])'/\\`\\$1\\`/g\" *.txt\n\nI think this is an improvement, assuming everyone is happy with the new\nMAN_BOLD_LITERAL default.\n\nI skimmed the diff and it looks there were no mis-conversions (I\nrecommend diff-highlight for this, as it makes it much easier to spot,\nthough perhaps --color-words would help, too).\n\n> diff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt\n> index e453132..cbae886 100644\n> --- a/Documentation/git-mv.txt\n> +++ b/Documentation/git-mv.txt\n> @@ -35,7 +35,7 @@ OPTIONS\n>          Skip move or rename actions which would lead to an error\n>  \tcondition. An error happens when a source is neither existing nor\n>  \tcontrolled by Git, or when it would overwrite an existing\n> -        file unless '-f' is given.\n> +        file unless `-f` is given.\n\ngit-am complains about the space indentation in the post-image. I know\nit was there before your patch, but the indentation for that paragraph\nis off. I wonder if it makes sense to fix it as a preliminary patch.\n\n-Peff\n"},{"id":"290312","messageId":"20160627190422.GC9594@sigill.intra.peff.net","threadId":"42725","inReplyTo":"20160627174623.11084-2-Matthieu.Moy@imag.fr","subject":"Re: [PATCH 2/6] doc: typeset long command-line options as literal","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-27T19:04:22Z","receivedAt":"2016-06-27T19:04:28Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Jun 27, 2016 at 07:46:19PM +0200, Matthieu Moy wrote:\n\n> Similarly to the previous commit, use backquotes instead of\n> forward-quotes, for long options.\n> \n> This was obtained with:\n> \n>   perl -pi -e \"s/'(--[a-z][a-z=<>-]*)'/\\`\\$1\\`/g\" *.txt\n> \n> and manual tweak to remove false positive in ascii-art (o'--o'--o' to\n> describe rewritten history).\n\nThese mostly looked good, but:\n\n>  grep.extendedRegexp::\n> -\tIf set to true, enable '--extended-regexp' option by default. This\n> -\toption is ignored when the `grep.patternType` option is set to a value\n> +\tIf set to true, enable `--extended-regexp` option by default. This\n> +\toption is ignored when the 'grep.patternType' option is set to a value\n\nWhat's going on in the second line here? We remove the backticks from\ngrep.patternType (which is not even a thing that should be touched by\nyour pattern).\n\n> @@ -1916,7 +1916,7 @@ log.decorate::\n>  \tcommand. If 'short' is specified, the ref name prefixes 'refs/heads/',\n>  \t'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is\n>  \tspecified, the full ref name (including prefix) will be printed.\n> -\tThis is the same as the log commands '--decorate' option.\n> +\tThis is the same as the log commands `--decorate` option.\n\nThis one conflicts applying on top of master, but the resolution is\nfairly straightforward.\n\n-Peff\n"},{"id":"290313","messageId":"20160627191005.GD9594@sigill.intra.peff.net","threadId":"42725","inReplyTo":"20160627174623.11084-3-Matthieu.Moy@imag.fr","subject":"Re: [PATCH 3/6] doc: typeset -- as litteral","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-27T19:10:05Z","receivedAt":"2016-06-27T19:10:20Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Jun 27, 2016 at 07:46:20PM +0200, Matthieu Moy wrote:\n\n> Subject: Re: [PATCH 3/6] doc: typeset -- as litteral\n\ns/litteral/literal/\n\nI can hardly blame you, though. I think English stole the word from\nFrench and then switched its spelling. :)\n\nYou may also want put quotes around \"--\" to make it clear that you are\ntalking about it as punctuation, not using it as such in your sentence.\n\nI read all the way through patch 6, and they all look good to me (though\nthe \"litteral\" typo appears again later). I won't bother responding to\neach separately.\n\nI do notice that your patterns are finding existing items marked with\nsingle-quotes. We may have other cases lurking that are not quoted at\nall (but should be). I think those could be a separate series, but if\nanybody wants to look for them, I think searching for \"\\--\" will help (a\nliteral double-dash needs that to avoid becoming an emdash).\n\n-Peff\n"},{"id":"290347","messageId":"vpqr3bhzqej.fsf@anie.imag.fr","threadId":"42725","inReplyTo":"20160627190422.GC9594@sigill.intra.peff.net","subject":"Re: [PATCH 2/6] doc: typeset long command-line options as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-06-28T08:08:52Z","receivedAt":"2016-06-28T08:09:17Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Jeff King <peff@peff.net> writes:\n\n> On Mon, Jun 27, 2016 at 07:46:19PM +0200, Matthieu Moy wrote:\n>\n>>  grep.extendedRegexp::\n>> -\tIf set to true, enable '--extended-regexp' option by default. This\n>> -\toption is ignored when the `grep.patternType` option is set to a value\n>> +\tIf set to true, enable `--extended-regexp` option by default. This\n>> +\toption is ignored when the 'grep.patternType' option is set to a value\n>\n> What's going on in the second line here? We remove the backticks from\n> grep.patternType (which is not even a thing that should be touched by\n> your pattern).\n\nNice catch. What happened was that I initially wrote the series on top\nof master, then rebased it on top of tr/doc-tt to avoid conflicts when\nJunio merges both. I did check that re-applying the perl substitution\nwas leading to the same patch, but apparently I did something wrong.\n\nI re-rechecked, re-found this instance and no other. Fixed in v2.\n\n>> @@ -1916,7 +1916,7 @@ log.decorate::\n>>  \tcommand. If 'short' is specified, the ref name prefixes 'refs/heads/',\n>>  \t'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is\n>>  \tspecified, the full ref name (including prefix) will be printed.\n>> -\tThis is the same as the log commands '--decorate' option.\n>> +\tThis is the same as the log commands `--decorate` option.\n>\n> This one conflicts applying on top of master, but the resolution is\n> fairly straightforward.\n\nSorry, I forgot to mention when sending the series: this is to be\napplied on top of tr/doc-tt (in next, marked \"will merge to master\").\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"290348","messageId":"vpqa8i5zpkd.fsf@anie.imag.fr","threadId":"42725","inReplyTo":"20160627191005.GD9594@sigill.intra.peff.net","subject":"Re: [PATCH 3/6] doc: typeset -- as litteral","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-06-28T08:26:58Z","receivedAt":"2016-06-28T08:27:25Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Jeff King <peff@peff.net> writes:\n\n> On Mon, Jun 27, 2016 at 07:46:20PM +0200, Matthieu Moy wrote:\n>\n>> Subject: Re: [PATCH 3/6] doc: typeset -- as litteral\n>\n> s/litteral/literal/\n>\n> I can hardly blame you, though. I think English stole the word from\n> French and then switched its spelling. :)\n\nI never remember about double consonent, and indeed the fact that French\nand English have different spelling for the same words doesn't help\n(addition Vs adition, traffic Vs trafic, ...) ;-).\n\nFixed in v2.\n\n> You may also want put quotes around \"--\" to make it clear that you are\n> talking about it as punctuation, not using it as such in your\n> sentence.\n\nDone.\n\n> I read all the way through patch 6, and they all look good to me (though\n> the \"litteral\" typo appears again later). I won't bother responding to\n> each separately.\n\nShould all be fixed now.\n\n> I do notice that your patterns are finding existing items marked with\n> single-quotes. We may have other cases lurking that are not quoted at\n> all (but should be).\n\nYes, this series (and tr/doc-tt) clearly catch just the low-hanging\nfruits. Having forward quotes in the existing text makes it clear that\nthe author wanted some kind of formatting, and hence make regex-based\nreplacement rather reliable (very few false positive).\n\nUnquoted stuff are more problematic since you can have for example\n\n  You should run `git foo --bar boz`\n\nor multi-lines formatted code blocks, and a naive regex would match\n--bar.\n\n> I think those could be a separate series, but if anybody wants to look\n> for them, I think searching for \"\\--\" will help (a literal double-dash\n> needs that to avoid becoming an emdash).\n\nThe rule seems to be more complex than this, for example \"Implies\n--porcelain\" in https://git-scm.com/docs/git-blame is properly typeset,\nalthough the source code has no escaping or quoting.\n\nI'll keep these out of the series for now, I've added more ideas to\n\n  https://git.wiki.kernel.org/index.php/SmallProjectsIdeas#Fix_asciidoc_formatting_in_documentation\n\nI may come back to this later.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"290349","messageId":"vpq60stzpco.fsf@anie.imag.fr","threadId":"42725","inReplyTo":"20160627185715.GB9594@sigill.intra.peff.net","subject":"Re: [PATCH 1/6] doc: typeset short command-line options as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-06-28T08:31:35Z","receivedAt":"2016-06-28T08:31:56Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Jeff King <peff@peff.net> writes:\n\n> On Mon, Jun 27, 2016 at 07:46:18PM +0200, Matthieu Moy wrote:\n>\n>> diff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt\n>> index e453132..cbae886 100644\n>> --- a/Documentation/git-mv.txt\n>> +++ b/Documentation/git-mv.txt\n>> @@ -35,7 +35,7 @@ OPTIONS\n>>          Skip move or rename actions which would lead to an error\n>>  \tcondition. An error happens when a source is neither existing nor\n>>  \tcontrolled by Git, or when it would overwrite an existing\n>> -        file unless '-f' is given.\n>> +        file unless `-f` is given.\n>\n> git-am complains about the space indentation in the post-image. I know\n> it was there before your patch, but the indentation for that paragraph\n> is off. I wonder if it makes sense to fix it as a preliminary patch.\n\nThere were just 2 mis-indented lines, I've added a preliminary patch to\nfix them.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"290365","messageId":"20160628114015.25828-8-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 7/7] doc: typeset HEAD and variants as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:15Z","receivedAt":"2016-06-28T11:41:45Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"This is an application of the newly added CodingGuidelines to HEAD and\nvariants like FETCH_HEAD. It was obtained with:\n\n  perl -pi -e \"s/'([A-Z_]*HEAD)'/\\`\\$1\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-bisect.txt        |  2 +-\n Documentation/git-branch.txt        |  4 ++--\n Documentation/git-cvsimport.txt     |  6 +++---\n Documentation/git-cvsserver.txt     |  2 +-\n Documentation/git-daemon.txt        |  2 +-\n Documentation/git-gui.txt           |  2 +-\n Documentation/git-ls-tree.txt       |  4 ++--\n Documentation/git-p4.txt            |  2 +-\n Documentation/git-tag.txt           |  2 +-\n Documentation/gitremote-helpers.txt |  2 +-\n Documentation/revisions.txt         | 24 ++++++++++++------------\n 11 files changed, 26 insertions(+), 26 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex d9f960b..2bb9a57 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -358,7 +358,7 @@ OPTIONS\n --no-checkout::\n +\n Do not checkout the new working tree at each iteration of the bisection\n-process. Instead just update a special reference named 'BISECT_HEAD' to make\n+process. Instead just update a special reference named `BISECT_HEAD` to make\n it point to the commit that should be tested.\n +\n This option may be useful when the test you would perform in each step\ndiff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt\nindex 123144f..1fe7344 100644\n--- a/Documentation/git-branch.txt\n+++ b/Documentation/git-branch.txt\n@@ -39,10 +39,10 @@ named commit).  With `--merged`, only branches merged into the named\n commit (i.e. the branches whose tip commits are reachable from the named\n commit) will be listed.  With `--no-merged` only branches not merged into\n the named commit will be listed.  If the <commit> argument is missing it\n-defaults to 'HEAD' (i.e. the tip of the current branch).\n+defaults to `HEAD` (i.e. the tip of the current branch).\n \n The command's second form creates a new branch head named <branchname>\n-which points to the current 'HEAD', or <start-point> if given.\n+which points to the current `HEAD`, or <start-point> if given.\n \n Note that this will create the new branch, but it will not switch the\n working tree to it; use \"git checkout <newbranch>\" to switch to the\ndiff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt\nindex bbf1c2b..41207a2 100644\n--- a/Documentation/git-cvsimport.txt\n+++ b/Documentation/git-cvsimport.txt\n@@ -74,10 +74,10 @@ OPTIONS\n \takin to the way 'git clone' uses 'origin' by default.\n \n -o <branch-for-HEAD>::\n-\tWhen no remote is specified (via -r) the 'HEAD' branch\n+\tWhen no remote is specified (via -r) the `HEAD` branch\n \tfrom CVS is imported to the 'origin' branch within the Git\n-\trepository, as 'HEAD' already has a special meaning for Git.\n-\tWhen a remote is specified the 'HEAD' branch is named\n+\trepository, as `HEAD` already has a special meaning for Git.\n+\tWhen a remote is specified the `HEAD` branch is named\n \tremotes/<remote>/master mirroring 'git clone' behaviour.\n \tUse this option if you want to import into a different\n \tbranch.\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex a1a5234..a336ae5 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -332,7 +332,7 @@ To get a checkout with the Eclipse CVS client:\n 3. Browse the 'modules' available. It will give you a list of the heads in\n    the repository. You will not be able to browse the tree from there. Only\n    the heads.\n-4. Pick 'HEAD' when it asks what branch/tag to check out. Untick the\n+4. Pick `HEAD` when it asks what branch/tag to check out. Untick the\n    \"launch commit wizard\" to avoid committing the .project file.\n \n Protocol notes: If you are using anonymous access via pserver, just select that.\ndiff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt\nindex 7901c54..3c91db7 100644\n--- a/Documentation/git-daemon.txt\n+++ b/Documentation/git-daemon.txt\n@@ -296,7 +296,7 @@ they correspond to these IP addresses.\n selectively enable/disable services per repository::\n \tTo enable 'git archive --remote' and disable 'git fetch' against\n \ta repository, have the following in the configuration file in the\n-\trepository (that is the file 'config' next to 'HEAD', 'refs' and\n+\trepository (that is the file 'config' next to `HEAD`, 'refs' and\n \t'objects').\n +\n ----------------------------------------------------------------\ndiff --git a/Documentation/git-gui.txt b/Documentation/git-gui.txt\nindex 8144527..c1a3e8b 100644\n--- a/Documentation/git-gui.txt\n+++ b/Documentation/git-gui.txt\n@@ -35,7 +35,7 @@ blame::\n \n browser::\n \tStart a tree browser showing all files in the specified\n-\tcommit (or 'HEAD' by default).  Files selected through the\n+\tcommit (or `HEAD` by default).  Files selected through the\n \tbrowser are opened in the blame viewer.\n \n citool::\ndiff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt\nindex a9f1909..dbc91f9 100644\n--- a/Documentation/git-ls-tree.txt\n+++ b/Documentation/git-ls-tree.txt\n@@ -27,9 +27,9 @@ in the current working directory.  Note that:\n    taken as relative to the current working directory.  E.g. when you are\n    in a directory 'sub' that has a directory 'dir', you can run 'git\n    ls-tree -r HEAD dir' to list the contents of the tree (that is\n-   'sub/dir' in 'HEAD').  You don't want to give a tree that is not at the\n+   'sub/dir' in `HEAD`).  You don't want to give a tree that is not at the\n    root level (e.g. `git ls-tree -r HEAD:sub dir`) in this case, as that\n-   would result in asking for 'sub/sub/dir' in the 'HEAD' commit.\n+   would result in asking for 'sub/sub/dir' in the `HEAD` commit.\n    However, the current working directory can be ignored by passing\n    --full-tree option.\n \ndiff --git a/Documentation/git-p4.txt b/Documentation/git-p4.txt\nindex 21c7af2..c83aaf3 100644\n--- a/Documentation/git-p4.txt\n+++ b/Documentation/git-p4.txt\n@@ -275,7 +275,7 @@ These options can be used to modify 'git p4 submit' behavior.\n --origin <commit>::\n \tUpstream location from which commits are identified to submit to\n \tp4.  By default, this is the most recent p4 commit reachable\n-\tfrom 'HEAD'.\n+\tfrom `HEAD`.\n \n -M::\n \tDetect renames.  See linkgit:git-diff[1].  Renames will be\ndiff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt\nindex 3225d0e..7ecca8e 100644\n--- a/Documentation/git-tag.txt\n+++ b/Documentation/git-tag.txt\n@@ -167,7 +167,7 @@ This option is only applicable when listing tags without annotation lines.\n \n --[no-]merged [<commit>]::\n \tOnly list tags whose tips are reachable, or not reachable\n-\tif `--no-merged` is used, from the specified commit ('HEAD'\n+\tif `--no-merged` is used, from the specified commit (`HEAD`\n \tif not specified).\n \n CONFIGURATION\ndiff --git a/Documentation/gitremote-helpers.txt b/Documentation/gitremote-helpers.txt\nindex 53ce1d0..a4de50a 100644\n--- a/Documentation/gitremote-helpers.txt\n+++ b/Documentation/gitremote-helpers.txt\n@@ -298,7 +298,7 @@ Supported if the helper has the \"fetch\" capability.\n \tis followed by a blank line). For example, the following would\n \tbe two batches of 'push', the first asking the remote-helper\n \tto push the local ref 'master' to the remote ref 'master' and\n-\tthe local 'HEAD' to the remote 'branch', and the second\n+\tthe local `HEAD` to the remote 'branch', and the second\n \tasking to push ref 'foo' to ref 'bar' (forced update requested\n \tby the '+').\n +\ndiff --git a/Documentation/revisions.txt b/Documentation/revisions.txt\nindex 15879b3..abae363 100644\n--- a/Documentation/revisions.txt\n+++ b/Documentation/revisions.txt\n@@ -28,8 +28,8 @@ blobs contained in a commit.\n   first match in the following rules:\n \n   . If '$GIT_DIR/<refname>' exists, that is what you mean (this is usually\n-    useful only for 'HEAD', 'FETCH_HEAD', 'ORIG_HEAD', 'MERGE_HEAD'\n-    and 'CHERRY_PICK_HEAD');\n+    useful only for `HEAD`, `FETCH_HEAD`, `ORIG_HEAD`, `MERGE_HEAD`\n+    and `CHERRY_PICK_HEAD`);\n \n   . otherwise, 'refs/<refname>' if it exists;\n \n@@ -41,16 +41,16 @@ blobs contained in a commit.\n \n   . otherwise, 'refs/remotes/<refname>/HEAD' if it exists.\n +\n-'HEAD' names the commit on which you based the changes in the working tree.\n-'FETCH_HEAD' records the branch which you fetched from a remote repository\n+`HEAD` names the commit on which you based the changes in the working tree.\n+`FETCH_HEAD` records the branch which you fetched from a remote repository\n with your last `git fetch` invocation.\n-'ORIG_HEAD' is created by commands that move your 'HEAD' in a drastic\n-way, to record the position of the 'HEAD' before their operation, so that\n+`ORIG_HEAD` is created by commands that move your `HEAD` in a drastic\n+way, to record the position of the `HEAD` before their operation, so that\n you can easily change the tip of the branch back to the state before you ran\n them.\n-'MERGE_HEAD' records the commit(s) which you are merging into your branch\n+`MERGE_HEAD` records the commit(s) which you are merging into your branch\n when you run `git merge`.\n-'CHERRY_PICK_HEAD' records the commit which you are cherry-picking\n+`CHERRY_PICK_HEAD` records the commit which you are cherry-picking\n when you run `git cherry-pick`.\n +\n Note that any of the 'refs/*' cases above may come either from\n@@ -59,7 +59,7 @@ While the ref name encoding is unspecified, UTF-8 is preferred as\n some output processing may assume ref names in UTF-8.\n \n '@'::\n-  '@' alone is a shortcut for 'HEAD'.\n+  '@' alone is a shortcut for `HEAD`.\n \n '<refname>@{<date>}', e.g. 'master@\\{yesterday\\}', 'HEAD@{5 minutes ago}'::\n   A ref followed by the suffix '@' with a date specification\n@@ -101,7 +101,7 @@ some output processing may assume ref names in UTF-8.\n '<branchname>@\\{push\\}', e.g. 'master@\\{push\\}', '@\\{push\\}'::\n   The suffix '@\\{push}' reports the branch \"where we would push to\" if\n   `git push` were run while `branchname` was checked out (or the current\n-  'HEAD' if no branchname is specified). Since our push destination is\n+  `HEAD` if no branchname is specified). Since our push destination is\n   in a remote repository, of course, we report the local tracking branch\n   that corresponds to that branch (i.e., something in 'refs/remotes/').\n +\n@@ -283,12 +283,12 @@ To summarize:\n '<rev1>..<rev2>'::\n \tInclude commits that are reachable from <rev2> but exclude\n \tthose that are reachable from <rev1>.  When either <rev1> or\n-\t<rev2> is omitted, it defaults to 'HEAD'.\n+\t<rev2> is omitted, it defaults to `HEAD`.\n \n '<rev1>\\...<rev2>'::\n \tInclude commits that are reachable from either <rev1> or\n \t<rev2> but exclude those that are reachable from both.  When\n-\teither <rev1> or <rev2> is omitted, it defaults to 'HEAD'.\n+\teither <rev1> or <rev2> is omitted, it defaults to `HEAD`.\n \n '<rev>{caret}@', e.g. 'HEAD{caret}@'::\n   A suffix '{caret}' followed by an at sign is the same as listing\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290366","messageId":"20160628114015.25828-6-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 5/7] doc: typeset long options with argument as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:13Z","receivedAt":"2016-06-28T11:41:54Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"We previously reformatted '--option' to `--option`. This patch reformats\n'--option <arg>' to `--option <arg>`. Obtained with:\n\n  perl -pi -e \"s/'(--[a-z][a-z=<>-]* <[^>]*>)'/\\`\\$1\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-config.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex 79905fb..f163113 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -47,12 +47,12 @@ checks or transformations are performed on the value.\n \n When reading, the values are read from the system, global and\n repository local configuration files by default, and options\n-`--system`, `--global`, `--local` and '--file <filename>' can be\n+`--system`, `--global`, `--local` and `--file <filename>` can be\n used to tell the command to read from only that location (see <<FILES>>).\n \n When writing, the new value is written to the repository local\n configuration file by default, and options `--system`, `--global`,\n-'--file <filename>' can be used to tell the command to write to\n+`--file <filename>` can be used to tell the command to write to\n that location (you can say `--local` but that is the default).\n \n This command will fail with non-zero status upon error.  Some exit\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290367","messageId":"20160628114015.25828-1-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160627174623.11084-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 0/7] literal formatting in documentation","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:08Z","receivedAt":"2016-06-28T11:41:57Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"This should address all comments from Peff.\n\nThe series is now based on master (which now contains tr/doc-tt).\n\nContent changes since v1:\n\n* First patch (fix indentation prior to actual change to avoid 'git\n  am' warning) is new.\n\n* One buggy replacement (`grep.patternType` -> 'grep.patternType')\n  removed.\n\nOther fixes are typos and details in commit messages.\n\nMatthieu Moy (7):\n  Documentation/git-mv.txt: fix whitespace indentation\n  doc: typeset short command-line options as literal\n  doc: typeset long command-line options as literal\n  doc: typeset '--' as literal\n  doc: typeset long options with argument as literal\n  CodingGuidelines: formatting HEAD in documentation\n  doc: typeset HEAD and variants as literal\n\n Documentation/CodingGuidelines           |  5 ++--\n Documentation/config.txt                 | 40 ++++++++++++++++----------------\n Documentation/diff-config.txt            |  2 +-\n Documentation/diff-format.txt            |  8 +++----\n Documentation/diff-generate-patch.txt    |  6 ++---\n Documentation/fetch-options.txt          |  6 ++---\n Documentation/git-am.txt                 |  4 ++--\n Documentation/git-bisect.txt             |  2 +-\n Documentation/git-branch.txt             |  6 ++---\n Documentation/git-cat-file.txt           | 12 +++++-----\n Documentation/git-checkout.txt           |  4 ++--\n Documentation/git-cherry-pick.txt        |  2 +-\n Documentation/git-clean.txt              |  2 +-\n Documentation/git-commit-tree.txt        |  2 +-\n Documentation/git-commit.txt             |  4 ++--\n Documentation/git-config.txt             | 28 +++++++++++-----------\n Documentation/git-credential-store.txt   |  2 +-\n Documentation/git-cvsimport.txt          | 12 +++++-----\n Documentation/git-cvsserver.txt          | 12 +++++-----\n Documentation/git-daemon.txt             |  8 +++----\n Documentation/git-describe.txt           |  2 +-\n Documentation/git-diff-index.txt         |  4 ++--\n Documentation/git-diff-tree.txt          | 20 ++++++++--------\n Documentation/git-difftool.txt           |  2 +-\n Documentation/git-fast-import.txt        |  4 ++--\n Documentation/git-fetch-pack.txt         |  4 ++--\n Documentation/git-filter-branch.txt      |  6 ++---\n Documentation/git-for-each-ref.txt       |  2 +-\n Documentation/git-fsck.txt               |  2 +-\n Documentation/git-grep.txt               | 10 ++++----\n Documentation/git-gui.txt                |  2 +-\n Documentation/git-help.txt               |  6 ++---\n Documentation/git-http-push.txt          |  4 ++--\n Documentation/git-interpret-trailers.txt |  2 +-\n Documentation/git-ls-files.txt           |  2 +-\n Documentation/git-ls-tree.txt            |  8 +++----\n Documentation/git-mktree.txt             |  2 +-\n Documentation/git-mv.txt                 |  4 ++--\n Documentation/git-notes.txt              |  2 +-\n Documentation/git-p4.txt                 | 22 +++++++++---------\n Documentation/git-push.txt               |  2 +-\n Documentation/git-rebase.txt             | 10 ++++----\n Documentation/git-remote.txt             | 10 ++++----\n Documentation/git-repack.txt             |  4 ++--\n Documentation/git-revert.txt             |  4 ++--\n Documentation/git-send-email.txt         | 24 +++++++++----------\n Documentation/git-send-pack.txt          | 10 ++++----\n Documentation/git-shell.txt              |  4 ++--\n Documentation/git-show-branch.txt        |  2 +-\n Documentation/git-show-ref.txt           |  6 ++---\n Documentation/git-svn.txt                | 26 ++++++++++-----------\n Documentation/git-tag.txt                |  2 +-\n Documentation/git-update-index.txt       | 14 +++++------\n Documentation/git-web--browse.txt        |  2 +-\n Documentation/git.txt                    | 10 ++++----\n Documentation/gitcore-tutorial.txt       |  2 +-\n Documentation/gitdiffcore.txt            |  4 ++--\n Documentation/gitk.txt                   |  2 +-\n Documentation/gitmodules.txt             |  2 +-\n Documentation/gitremote-helpers.txt      | 10 ++++----\n Documentation/rev-list-options.txt       |  2 +-\n Documentation/revisions.txt              | 26 ++++++++++-----------\n 62 files changed, 228 insertions(+), 227 deletions(-)\n\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290368","messageId":"20160628114015.25828-2-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 1/7] Documentation/git-mv.txt: fix whitespace indentation","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:09Z","receivedAt":"2016-06-28T11:41:59Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Replace spaces with tabs to avoid a warning when further patches change\nthese lines.\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-mv.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt\nindex e453132..6dcb8b2 100644\n--- a/Documentation/git-mv.txt\n+++ b/Documentation/git-mv.txt\n@@ -32,10 +32,10 @@ OPTIONS\n --force::\n \tForce renaming or moving of a file even if the target exists\n -k::\n-        Skip move or rename actions which would lead to an error\n+\tSkip move or rename actions which would lead to an error\n \tcondition. An error happens when a source is neither existing nor\n \tcontrolled by Git, or when it would overwrite an existing\n-        file unless '-f' is given.\n+\tfile unless '-f' is given.\n -n::\n --dry-run::\n \tDo nothing; only show what would happen\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290369","messageId":"20160628114015.25828-5-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 4/7] doc: typeset '--' as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:12Z","receivedAt":"2016-06-28T11:42:00Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"This was obtained with:\n\n  perl -pi -e \"s/'--'/\\`--\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/git-fast-import.txt   | 4 ++--\n Documentation/git-filter-branch.txt | 2 +-\n Documentation/rev-list-options.txt  | 2 +-\n 3 files changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt\nindex 644df99..2b76265 100644\n--- a/Documentation/git-fast-import.txt\n+++ b/Documentation/git-fast-import.txt\n@@ -1056,7 +1056,7 @@ relative-marks::\n no-relative-marks::\n force::\n \tAct as though the corresponding command-line option with\n-\ta leading '--' was passed on the command line\n+\ta leading `--` was passed on the command line\n \t(see OPTIONS, above).\n \n import-marks::\n@@ -1107,7 +1107,7 @@ options the user may specify to git fast-import itself.\n \n The `<option>` part of the command may contain any of the options\n listed in the OPTIONS section that do not change import semantics,\n-without the leading '--' and is treated in the same way.\n+without the leading `--` and is treated in the same way.\n \n Option commands must be the first commands on the input (not counting\n feature commands), to give an option command after any non-option\ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex 060ebb3..0a09698 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -197,7 +197,7 @@ to other tags will be rewritten to point to the underlying commit.\n <rev-list options>...::\n \tArguments for 'git rev-list'.  All positive refs included by\n \tthese options are rewritten.  You may also specify options\n-\tsuch as `--all`, but you must use '--' to separate them from\n+\tsuch as `--all`, but you must use `--` to separate them from\n \tthe 'git filter-branch' options. Implies <<Remap_to_ancestor>>.\n \n \ndiff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt\nindex 4f009d4..c5bd218 100644\n--- a/Documentation/rev-list-options.txt\n+++ b/Documentation/rev-list-options.txt\n@@ -193,7 +193,7 @@ endif::git-rev-list[]\n \n --stdin::\n \tIn addition to the '<commit>' listed on the command\n-\tline, read them from the standard input. If a '--' separator is\n+\tline, read them from the standard input. If a `--` separator is\n \tseen, stop reading commits and start reading paths to limit the\n \tresult.\n \n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290370","messageId":"20160628114015.25828-4-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 3/7] doc: typeset long command-line options as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:11Z","receivedAt":"2016-06-28T11:42:09Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Similarly to the previous commit, use backquotes instead of\nforward-quotes, for long options.\n\nThis was obtained with:\n\n  perl -pi -e \"s/'(--[a-z][a-z=<>-]*)'/\\`\\$1\\`/g\" *.txt\n\nand manual tweak to remove false positive in ascii-art (o'--o'--o' to\ndescribe rewritten history).\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/config.txt                 | 32 ++++++++++++++++----------------\n Documentation/diff-format.txt            |  2 +-\n Documentation/diff-generate-patch.txt    |  4 ++--\n Documentation/fetch-options.txt          |  6 +++---\n Documentation/git-am.txt                 |  4 ++--\n Documentation/git-branch.txt             |  2 +-\n Documentation/git-cat-file.txt           |  2 +-\n Documentation/git-cherry-pick.txt        |  2 +-\n Documentation/git-commit.txt             |  2 +-\n Documentation/git-config.txt             | 26 +++++++++++++-------------\n Documentation/git-credential-store.txt   |  2 +-\n Documentation/git-cvsserver.txt          |  2 +-\n Documentation/git-daemon.txt             |  6 +++---\n Documentation/git-describe.txt           |  2 +-\n Documentation/git-diff-index.txt         |  4 ++--\n Documentation/git-diff-tree.txt          |  6 +++---\n Documentation/git-difftool.txt           |  2 +-\n Documentation/git-fetch-pack.txt         |  2 +-\n Documentation/git-filter-branch.txt      |  4 ++--\n Documentation/git-for-each-ref.txt       |  2 +-\n Documentation/git-fsck.txt               |  2 +-\n Documentation/git-grep.txt               |  8 ++++----\n Documentation/git-help.txt               |  6 +++---\n Documentation/git-http-push.txt          |  4 ++--\n Documentation/git-interpret-trailers.txt |  2 +-\n Documentation/git-ls-files.txt           |  2 +-\n Documentation/git-p4.txt                 | 20 ++++++++++----------\n Documentation/git-push.txt               |  2 +-\n Documentation/git-rebase.txt             | 10 +++++-----\n Documentation/git-remote.txt             | 10 +++++-----\n Documentation/git-revert.txt             |  4 ++--\n Documentation/git-send-email.txt         | 24 ++++++++++++------------\n Documentation/git-send-pack.txt          | 10 +++++-----\n Documentation/git-show-branch.txt        |  2 +-\n Documentation/git-show-ref.txt           |  6 +++---\n Documentation/git-svn.txt                | 26 +++++++++++++-------------\n Documentation/git-tag.txt                |  2 +-\n Documentation/git-update-index.txt       | 14 +++++++-------\n Documentation/git-web--browse.txt        |  2 +-\n Documentation/git.txt                    |  8 ++++----\n Documentation/gitcore-tutorial.txt       |  2 +-\n Documentation/gitdiffcore.txt            |  4 ++--\n Documentation/gitk.txt                   |  2 +-\n Documentation/gitmodules.txt             |  2 +-\n Documentation/gitremote-helpers.txt      |  8 ++++----\n Documentation/revisions.txt              |  2 +-\n 46 files changed, 149 insertions(+), 149 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 6d5e5ba..556ed0e 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -140,7 +140,7 @@ boolean::\n        false;; Boolean false can be spelled as `no`, `off`,\n \t\t`false`, or `0`.\n +\n-When converting value to the canonical form using '--bool' type\n+When converting value to the canonical form using `--bool` type\n specifier; 'git config' will ensure that the output is \"true\" or\n \"false\" (spelled in lowercase).\n \n@@ -481,7 +481,7 @@ core.worktree::\n \tIf `GIT_COMMON_DIR` environment variable is set, core.worktree\n \tis ignored and not used for determining the root of working tree.\n \tThis can be overridden by the `GIT_WORK_TREE` environment\n-\tvariable and the '--work-tree' command-line option.\n+\tvariable and the `--work-tree` command-line option.\n \tThe value can be an absolute path or relative to the path to\n \tthe .git directory, which is either specified by --git-dir\n \tor GIT_DIR, or automatically discovered.\n@@ -779,7 +779,7 @@ core.abbrev::\n add.ignoreErrors::\n add.ignore-errors (deprecated)::\n \tTells 'git add' to continue adding files when some files cannot be\n-\tadded due to indexing errors. Equivalent to the '--ignore-errors'\n+\tadded due to indexing errors. Equivalent to the `--ignore-errors`\n \toption of linkgit:git-add[1].  `add.ignore-errors` is deprecated,\n \tas it does not follow the usual naming convention for configuration\n \tvariables.\n@@ -805,9 +805,9 @@ from the original current directory. See linkgit:git-rev-parse[1].\n \n am.keepcr::\n \tIf true, git-am will call git-mailsplit for patches in mbox format\n-\twith parameter '--keep-cr'. In this case git-mailsplit will\n+\twith parameter `--keep-cr`. In this case git-mailsplit will\n \tnot remove `\\r` from lines ending with `\\r\\n`. Can be overridden\n-\tby giving '--no-keep-cr' from the command line.\n+\tby giving `--no-keep-cr` from the command line.\n \tSee linkgit:git-am[1], linkgit:git-mailsplit[1].\n \n am.threeWay::\n@@ -820,7 +820,7 @@ am.threeWay::\n \n apply.ignoreWhitespace::\n \tWhen set to 'change', tells 'git apply' to ignore changes in\n-\twhitespace, in the same way as the '--ignore-space-change'\n+\twhitespace, in the same way as the `--ignore-space-change`\n \toption.\n \tWhen set to one of: no, none, never, false tells 'git apply' to\n \trespect all whitespace differences.\n@@ -828,7 +828,7 @@ apply.ignoreWhitespace::\n \n apply.whitespace::\n \tTells 'git apply' how to handle whitespaces, in the same way\n-\tas the '--whitespace' option. See linkgit:git-apply[1].\n+\tas the `--whitespace` option. See linkgit:git-apply[1].\n \n branch.autoSetupMerge::\n \tTells 'git branch' and 'git checkout' to set up new branches\n@@ -1505,12 +1505,12 @@ grep.lineNumber::\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\n-\t'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',\n-\t'--fixed-strings', or '--perl-regexp' option accordingly, while the\n+\t'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,\n+\t`--fixed-strings`, or `--perl-regexp` option accordingly, while the\n \tvalue 'default' will return to the default matching behavior.\n \n grep.extendedRegexp::\n-\tIf set to true, enable '--extended-regexp' option by default. This\n+\tIf set to true, enable `--extended-regexp` option by default. This\n \toption is ignored when the `grep.patternType` option is set to a value\n \tother than 'default'.\n \n@@ -1967,7 +1967,7 @@ log.decorate::\n \tspecified, the full ref name (including prefix) will be printed.\n \tIf 'auto' is specified, then if the output is going to a terminal,\n \tthe ref names are shown as if 'short' were given, otherwise no ref\n-\tnames are shown. This is the same as the '--decorate' option\n+\tnames are shown. This is the same as the `--decorate` option\n \tof the `git log`.\n \n log.follow::\n@@ -2350,16 +2350,16 @@ new default).\n --\n \n push.followTags::\n-\tIf set to true enable '--follow-tags' option by default.  You\n+\tIf set to true enable `--follow-tags` option by default.  You\n \tmay override this configuration at time of push by specifying\n-\t'--no-follow-tags'.\n+\t`--no-follow-tags`.\n \n push.gpgSign::\n \tMay be set to a boolean value, or the string 'if-asked'. A true\n-\tvalue causes all pushes to be GPG signed, as if '--signed' is\n+\tvalue causes all pushes to be GPG signed, as if `--signed` is\n \tpassed to linkgit:git-push[1]. The string 'if-asked' causes\n \tpushes to be signed if the server supports it, as if\n-\t'--signed=if-asked' is passed to 'git push'. A false value may\n+\t`--signed=if-asked` is passed to 'git push'. A false value may\n \toverride a value from a lower-priority config file. An explicit\n \tcommand-line flag always overrides this config option.\n \n@@ -2382,7 +2382,7 @@ rebase.stat::\n \trebase. False by default.\n \n rebase.autoSquash::\n-\tIf set to true enable '--autosquash' option by default.\n+\tIf set to true enable `--autosquash` option by default.\n \n rebase.autoStash::\n \tWhen set to true, automatically create a temporary stash\ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\nindex f10fd54..cf52626 100644\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -86,7 +86,7 @@ diff format for merges\n ----------------------\n \n \"git-diff-tree\", \"git-diff-files\" and \"git-diff --raw\"\n-can take `-c` or '--cc' option\n+can take `-c` or `--cc` option\n to generate diff output also for merge commits.  The output differs\n from the format described above in the following way:\n \ndiff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt\nindex 18608f5..d2a7ff5 100644\n--- a/Documentation/diff-generate-patch.txt\n+++ b/Documentation/diff-generate-patch.txt\n@@ -2,7 +2,7 @@ Generating patches with -p\n --------------------------\n \n When \"git-diff-index\", \"git-diff-tree\", or \"git-diff-files\" are run\n-with a `-p` option, \"git diff\" without the '--raw' option, or\n+with a `-p` option, \"git diff\" without the `--raw` option, or\n \"git log\" with the \"-p\" option, they\n do not produce the output described above; instead they produce a\n patch file.  You can customize the creation of such patches via the\n@@ -118,7 +118,7 @@ index fabadb8,cc95eb0..4866510\n \n        diff --combined file\n +\n-or like this (when '--cc' option is used):\n+or like this (when `--cc` option is used):\n \n        diff --cc file\n \ndiff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt\nindex b05a834..9eab1f5 100644\n--- a/Documentation/fetch-options.txt\n+++ b/Documentation/fetch-options.txt\n@@ -88,7 +88,7 @@ ifndef::git-pull[]\n \tto whatever else would otherwise be fetched.  Using this\n \toption alone does not subject tags to pruning, even if --prune\n \tis used (though tags may be pruned anyway if they are also the\n-\tdestination of an explicit refspec; see '--prune').\n+\tdestination of an explicit refspec; see `--prune`).\n \n --recurse-submodules[=yes|on-demand|no]::\n \tThis option controls if and under what conditions new commits of\n@@ -110,7 +110,7 @@ ifndef::git-pull[]\n \n --no-recurse-submodules::\n \tDisable recursive fetching of submodules (this has the same effect as\n-\tusing the '--recurse-submodules=no' option).\n+\tusing the `--recurse-submodules=no` option).\n \n --submodule-prefix=<path>::\n \tPrepend <path> to paths printed in informative messages\n@@ -137,7 +137,7 @@ endif::git-pull[]\n \n --upload-pack <upload-pack>::\n \tWhen given, and the repository to fetch from is handled\n-\tby 'git fetch-pack', '--exec=<upload-pack>' is passed to\n+\tby 'git fetch-pack', `--exec=<upload-pack>` is passed to\n \tthe command to specify non-default path for the command\n \trun on the other end.\n \ndiff --git a/Documentation/git-am.txt b/Documentation/git-am.txt\nindex 13cdd7f..8dd9e4f 100644\n--- a/Documentation/git-am.txt\n+++ b/Documentation/git-am.txt\n@@ -198,12 +198,12 @@ When initially invoking `git am`, you give it the names of the mailboxes\n to process.  Upon seeing the first patch that does not apply, it\n aborts in the middle.  You can recover from this in one of two ways:\n \n-. skip the current patch by re-running the command with the '--skip'\n+. skip the current patch by re-running the command with the `--skip`\n   option.\n \n . hand resolve the conflict in the working directory, and update\n   the index file to bring it into a state that the patch should\n-  have produced.  Then run the command with the '--continue' option.\n+  have produced.  Then run the command with the `--continue` option.\n \n The command refuses to process new mailboxes until the current\n operation is finished, so if you decide to start over from scratch,\ndiff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt\nindex 4a7037f..123144f 100644\n--- a/Documentation/git-branch.txt\n+++ b/Documentation/git-branch.txt\n@@ -172,7 +172,7 @@ This option is only applicable in non-verbose mode.\n +\n This behavior is the default when the start point is a remote-tracking branch.\n Set the branch.autoSetupMerge configuration variable to `false` if you\n-want `git checkout` and `git branch` to always behave as if '--no-track'\n+want `git checkout` and `git branch` to always behave as if `--no-track`\n were given. Set it to `always` if you want this behavior when the\n start-point is either a local or remote-tracking branch.\n \ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex f8d0dcf..18d03d8 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -16,7 +16,7 @@ DESCRIPTION\n -----------\n In its first form, the command provides the content or the type of an object in\n the repository. The type is required unless `-t` or `-p` is used to find the\n-object type, or `-s` is used to find the object size, or '--textconv' is used\n+object type, or `-s` is used to find the object size, or `--textconv` is used\n (which implies type \"blob\").\n \n In the second form, a list of objects (separated by linefeeds) is provided on\ndiff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt\nindex c104a59..d35d771 100644\n--- a/Documentation/git-cherry-pick.txt\n+++ b/Documentation/git-cherry-pick.txt\n@@ -47,7 +47,7 @@ OPTIONS\n \tFor a more complete list of ways to spell commits, see\n \tlinkgit:gitrevisions[7].\n \tSets of commits can be passed but no traversal is done by\n-\tdefault, as if the '--no-walk' option was specified, see\n+\tdefault, as if the `--no-walk` option was specified, see\n \tlinkgit:git-rev-list[1]. Note that specifying a range will\n \tfeed all <commit>... arguments to a single revision walk\n \t(see a later example that uses 'maint master..next').\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex e295d49..b0a294d 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -260,7 +260,7 @@ FROM UPSTREAM REBASE\" section in linkgit:git-rebase[1].)\n \tstaged for other paths. This is the default mode of operation of\n \t'git commit' if any paths are given on the command line,\n \tin which case this option can be omitted.\n-\tIf this option is specified together with '--amend', then\n+\tIf this option is specified together with `--amend`, then\n \tno paths need to be specified, which can be used to amend\n \tthe last commit without committing changes that have\n \talready been staged.\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex a89c304..79905fb 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -31,29 +31,29 @@ You can query/set/replace/unset options with this command. The name is\n actually the section and the key separated by a dot, and the value will be\n escaped.\n \n-Multiple lines can be added to an option by using the '--add' option.\n+Multiple lines can be added to an option by using the `--add` option.\n If you want to update or unset an option which can occur on multiple\n lines, a POSIX regexp `value_regex` needs to be given.  Only the\n existing values that match the regexp are updated or unset.  If\n you want to handle the lines that do *not* match the regex, just\n prepend a single exclamation mark in front (see also <<EXAMPLES>>).\n \n-The type specifier can be either '--int' or '--bool', to make\n+The type specifier can be either `--int` or `--bool`, to make\n 'git config' ensure that the variable(s) are of the given type and\n convert the value to the canonical form (simple decimal number for int,\n-a \"true\" or \"false\" string for bool), or '--path', which does some\n-path expansion (see '--path' below).  If no type specifier is passed, no\n+a \"true\" or \"false\" string for bool), or `--path`, which does some\n+path expansion (see `--path` below).  If no type specifier is passed, no\n checks or transformations are performed on the value.\n \n When reading, the values are read from the system, global and\n repository local configuration files by default, and options\n-'--system', '--global', '--local' and '--file <filename>' can be\n+`--system`, `--global`, `--local` and '--file <filename>' can be\n used to tell the command to read from only that location (see <<FILES>>).\n \n When writing, the new value is written to the repository local\n-configuration file by default, and options '--system', '--global',\n+configuration file by default, and options `--system`, `--global`,\n '--file <filename>' can be used to tell the command to write to\n-that location (you can say '--local' but that is the default).\n+that location (you can say `--local` but that is the default).\n \n This command will fail with non-zero status upon error.  Some exit\n codes are:\n@@ -138,7 +138,7 @@ See also <<FILES>>.\n \tUse the given config file instead of the one specified by GIT_CONFIG.\n \n --blob blob::\n-\tSimilar to '--file' but use the given blob instead of a file. E.g.\n+\tSimilar to `--file` but use the given blob instead of a file. E.g.\n \tyou can use 'master:.gitmodules' to read values from the file\n \t'.gitmodules' in the master branch. See \"SPECIFYING REVISIONS\"\n \tsection in linkgit:gitrevisions[7] for a more complete list of\n@@ -220,7 +220,7 @@ See also <<FILES>>.\n -e::\n --edit::\n \tOpens an editor to modify the specified config file; either\n-\t'--system', '--global', or repository (default).\n+\t`--system`, `--global`, or repository (default).\n \n --[no-]includes::\n \tRespect `include.*` directives in config files when looking up\n@@ -232,7 +232,7 @@ See also <<FILES>>.\n FILES\n -----\n \n-If not set explicitly with '--file', there are four files where\n+If not set explicitly with `--file`, there are four files where\n 'git config' will search for configuration options:\n \n $(prefix)/etc/gitconfig::\n@@ -264,11 +264,11 @@ precedence over values read earlier.  When multiple values are taken then all\n values of a key from all files will be used.\n \n All writing options will per default write to the repository specific\n-configuration file. Note that this also affects options like '--replace-all'\n-and '--unset'. *'git config' will only ever change one file at a time*.\n+configuration file. Note that this also affects options like `--replace-all`\n+and `--unset`. *'git config' will only ever change one file at a time*.\n \n You can override these rules either by command-line options or by environment\n-variables. The '--global' and the '--system' options will limit the file used\n+variables. The `--global` and the `--system` options will limit the file used\n to the global or system-wide file respectively. The `GIT_CONFIG` environment\n variable has a similar effect, but you can specify any filename you want.\n \ndiff --git a/Documentation/git-credential-store.txt b/Documentation/git-credential-store.txt\nindex e3c8f27..25fb963 100644\n--- a/Documentation/git-credential-store.txt\n+++ b/Documentation/git-credential-store.txt\n@@ -44,7 +44,7 @@ OPTIONS\n FILES\n -----\n \n-If not set explicitly with '--file', there are two files where\n+If not set explicitly with `--file`, there are two files where\n git-credential-store will search for credentials in order of precedence:\n \n ~/.git-credentials::\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex 5e3c6a8..a1a5234 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -54,7 +54,7 @@ Print usage information and exit\n You can specify a list of allowed directories. If no directories\n are given, all are allowed. This is an additional restriction, gitcvs\n access still needs to be enabled by the `gitcvs.enabled` config option\n-unless '--export-all' was given, too.\n+unless `--export-all` was given, too.\n \n \n DESCRIPTION\ndiff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt\nindex dc20275..7901c54 100644\n--- a/Documentation/git-daemon.txt\n+++ b/Documentation/git-daemon.txt\n@@ -30,7 +30,7 @@ that service if it is enabled.\n \n It verifies that the directory has the magic file \"git-daemon-export-ok\", and\n it will refuse to export any Git directory that hasn't explicitly been marked\n-for export this way (unless the '--export-all' parameter is specified). If you\n+for export this way (unless the `--export-all` parameter is specified). If you\n pass some directory paths as 'git daemon' arguments, you can further restrict\n the offers to a whitelist comprising of those.\n \n@@ -90,10 +90,10 @@ OPTIONS\n \tis not supported, then --listen=hostname is also not supported and\n \t--listen must be given an IPv4 address.\n \tCan be given more than once.\n-\tIncompatible with '--inetd' option.\n+\tIncompatible with `--inetd` option.\n \n --port=<n>::\n-\tListen on an alternative port.  Incompatible with '--inetd' option.\n+\tListen on an alternative port.  Incompatible with `--inetd` option.\n \n --init-timeout=<n>::\n \tTimeout (in seconds) between the moment the connection is established\ndiff --git a/Documentation/git-describe.txt b/Documentation/git-describe.txt\nindex c8f28c8..e4ac448 100644\n--- a/Documentation/git-describe.txt\n+++ b/Documentation/git-describe.txt\n@@ -154,7 +154,7 @@ is found, its name will be output and searching will stop.\n If an exact match was not found, 'git describe' will walk back\n through the commit history to locate an ancestor commit which\n has been tagged.  The ancestor's tag will be output along with an\n-abbreviation of the input commit-ish's SHA-1. If '--first-parent' was\n+abbreviation of the input commit-ish's SHA-1. If `--first-parent` was\n specified then the walk will only consider the first parent of each\n commit.\n \ndiff --git a/Documentation/git-diff-index.txt b/Documentation/git-diff-index.txt\nindex a86cf62..a171506 100644\n--- a/Documentation/git-diff-index.txt\n+++ b/Documentation/git-diff-index.txt\n@@ -40,13 +40,13 @@ include::diff-format.txt[]\n Operating Modes\n ---------------\n You can choose whether you want to trust the index file entirely\n-(using the '--cached' flag) or ask the diff logic to show any files\n+(using the `--cached` flag) or ask the diff logic to show any files\n that don't match the stat state as being \"tentatively changed\".  Both\n of these operations are very useful indeed.\n \n Cached Mode\n -----------\n-If '--cached' is specified, it allows you to ask:\n+If `--cached` is specified, it allows you to ask:\n \n \tshow me the differences between HEAD and the current index\n \tcontents (the ones I'd write using 'git write-tree')\ndiff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt\nindex 7558e49..7870e17 100644\n--- a/Documentation/git-diff-tree.txt\n+++ b/Documentation/git-diff-tree.txt\n@@ -43,11 +43,11 @@ include::diff-options.txt[]\n \tshow tree entry itself as well as subtrees.  Implies -r.\n \n --root::\n-\tWhen '--root' is specified the initial commit will be shown as a big\n+\tWhen `--root` is specified the initial commit will be shown as a big\n \tcreation event. This is equivalent to a diff against the NULL tree.\n \n --stdin::\n-\tWhen '--stdin' is specified, the command does not take\n+\tWhen `--stdin` is specified, the command does not take\n \t<tree-ish> arguments from the command line.  Instead, it\n \treads lines containing either two <tree>, one <commit>, or a\n \tlist of <commit> from its standard input.  (Use a single space\n@@ -91,7 +91,7 @@ include::pretty-options.txt[]\n -c::\n \tThis flag changes the way a merge commit is displayed\n \t(which means it is useful only when the command is given\n-\tone <tree-ish>, or '--stdin').  It shows the differences\n+\tone <tree-ish>, or `--stdin`).  It shows the differences\n \tfrom each of the parents to the merge result simultaneously\n \tinstead of showing pairwise diff between a parent and the\n \tresult one at a time (which is what the `-m` option does).\ndiff --git a/Documentation/git-difftool.txt b/Documentation/git-difftool.txt\nindex 333cf6f..224fb30 100644\n--- a/Documentation/git-difftool.txt\n+++ b/Documentation/git-difftool.txt\n@@ -98,7 +98,7 @@ instead.  `--no-symlinks` is the default on Windows.\n \tinvoked diff tool returns a non-zero exit code.\n +\n 'git-difftool' will forward the exit code of the invoked tool when\n-'--trust-exit-code' is used.\n+`--trust-exit-code` is used.\n \n See linkgit:git-diff[1] for the full list of supported options.\n \ndiff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt\nindex 4c8219d..24417ee 100644\n--- a/Documentation/git-fetch-pack.txt\n+++ b/Documentation/git-fetch-pack.txt\n@@ -41,7 +41,7 @@ OPTIONS\n \toption, then the refs from stdin are processed after those\n \ton the command line.\n +\n-If '--stateless-rpc' is specified together with this option then\n+If `--stateless-rpc` is specified together with this option then\n the list of refs must be in packet format (pkt-line). Each ref must\n be in a separate packet, and the list must end with a flush packet.\n \ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex 2d30297..060ebb3 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -171,7 +171,7 @@ to other tags will be rewritten to point to the underlying commit.\n \tuntouched.  This switch allow git-filter-branch to ignore such\n \tcommits.  Though, this switch only applies for commits that have one\n \tand only one parent, it will hence keep merges points. Also, this\n-\toption is not compatible with the use of '--commit-filter'. Though you\n+\toption is not compatible with the use of `--commit-filter`. Though you\n \tjust need to use the function 'git_commit_non_empty_tree \"$@\"' instead\n \tof the `git commit-tree \"$@\"` idiom in your commit filter to make that\n \thappen.\n@@ -197,7 +197,7 @@ to other tags will be rewritten to point to the underlying commit.\n <rev-list options>...::\n \tArguments for 'git rev-list'.  All positive refs included by\n \tthese options are rewritten.  You may also specify options\n-\tsuch as '--all', but you must use '--' to separate them from\n+\tsuch as `--all`, but you must use '--' to separate them from\n \tthe 'git filter-branch' options. Implies <<Remap_to_ancestor>>.\n \n \ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex d9d406d..f57e69b 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -142,7 +142,7 @@ align::\n \t<width> and <position> used instead.  For instance,\n \t`%(align:<width>,<position>)`. If the contents length is more\n \tthan the width then no alignment is performed. If used with\n-\t'--quote' everything in between %(align:...) and %(end) is\n+\t`--quote` everything in between %(align:...) and %(end) is\n \tquoted, but if nested then only the topmost level performs\n \tquoting.\n \ndiff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt\nindex 84ee92e..7fc68eb 100644\n--- a/Documentation/git-fsck.txt\n+++ b/Documentation/git-fsck.txt\n@@ -95,7 +95,7 @@ DISCUSSION\n git-fsck tests SHA-1 and general object sanity, and it does full tracking\n of the resulting reachability and everything else. It prints out any\n corruption it finds (missing or bad objects), and if you use the\n-'--unreachable' flag it will also print out objects that exist but that\n+`--unreachable` flag it will also print out objects that exist but that\n aren't reachable from any of the specified head nodes (or the default\n set, as mentioned above).\n \ndiff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt\nindex 557973b..0ecea6e 100644\n--- a/Documentation/git-grep.txt\n+++ b/Documentation/git-grep.txt\n@@ -45,12 +45,12 @@ grep.lineNumber::\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\n-\t'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',\n-\t'--fixed-strings', or '--perl-regexp' option accordingly, while the\n+\t'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,\n+\t`--fixed-strings`, or `--perl-regexp` option accordingly, while the\n \tvalue 'default' will return to the default matching behavior.\n \n grep.extendedRegexp::\n-\tIf set to true, enable '--extended-regexp' option by default. This\n+\tIf set to true, enable `--extended-regexp` option by default. This\n \toption is ignored when the `grep.patternType` option is set to a value\n \tother than 'default'.\n \n@@ -59,7 +59,7 @@ grep.threads::\n \t8 threads are used by default (for now).\n \n grep.fullName::\n-\tIf set to true, enable '--full-name' option by default.\n+\tIf set to true, enable `--full-name` option by default.\n \n grep.fallbackToNoIndex::\n \tIf set to true, fall back to git grep --no-index if git grep\ndiff --git a/Documentation/git-help.txt b/Documentation/git-help.txt\nindex c6f7ce7..40d328a 100644\n--- a/Documentation/git-help.txt\n+++ b/Documentation/git-help.txt\n@@ -18,10 +18,10 @@ With no options and no COMMAND or GUIDE given, the synopsis of the 'git'\n command and a list of the most commonly used Git commands are printed\n on the standard output.\n \n-If the option '--all' or `-a` is given, all available commands are\n+If the option `--all` or `-a` is given, all available commands are\n printed on the standard output.\n \n-If the option '--guide' or `-g` is given, a list of the useful\n+If the option `--guide` or `-g` is given, a list of the useful\n Git guides is also printed on the standard output.\n \n If a command, or a guide, is given, a manual page for that command or\n@@ -176,7 +176,7 @@ Note about git config --global\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n Note that all these configuration variables should probably be set\n-using the '--global' flag, for example like this:\n+using the `--global` flag, for example like this:\n \n ------------------------------------------------\n $ git config --global help.format web\ndiff --git a/Documentation/git-http-push.txt b/Documentation/git-http-push.txt\nindex 2e67362..2aceb6f 100644\n--- a/Documentation/git-http-push.txt\n+++ b/Documentation/git-http-push.txt\n@@ -81,13 +81,13 @@ destination side.\n      exist in the set of remote refs; the ref matched <src>\n      locally is used as the name of the destination.\n \n-Without '--force', the <src> ref is stored at the remote only if\n+Without `--force`, the <src> ref is stored at the remote only if\n <dst> does not exist, or <dst> is a proper subset (i.e. an\n ancestor) of <src>.  This check, known as \"fast-forward check\",\n is performed in order to avoid accidentally overwriting the\n remote ref and lose other peoples' commits from there.\n \n-With '--force', the fast-forward check is disabled for all refs.\n+With `--force`, the fast-forward check is disabled for all refs.\n \n Optionally, a <ref> parameter can be prefixed with a plus '+' sign\n to disable the fast-forward check only on that ref.\ndiff --git a/Documentation/git-interpret-trailers.txt b/Documentation/git-interpret-trailers.txt\nindex a77b901..93d1db6 100644\n--- a/Documentation/git-interpret-trailers.txt\n+++ b/Documentation/git-interpret-trailers.txt\n@@ -219,7 +219,7 @@ Signed-off-by: Alice <alice@example.com>\n Signed-off-by: Bob <bob@example.com>\n ------------\n \n-* Use the '--in-place' option to edit a message file in place:\n+* Use the `--in-place` option to edit a message file in place:\n +\n ------------\n $ cat msg.txt\ndiff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt\nindex 75c3f41..078b556 100644\n--- a/Documentation/git-ls-files.txt\n+++ b/Documentation/git-ls-files.txt\n@@ -175,7 +175,7 @@ followed by the  (\"attr/<eolattr>\").\n \n Output\n ------\n-'git ls-files' just outputs the filenames unless '--stage' is specified in\n+'git ls-files' just outputs the filenames unless `--stage` is specified in\n which case it outputs:\n \n         [<tag> ]<mode> <object> <stage> <file>\ndiff --git a/Documentation/git-p4.txt b/Documentation/git-p4.txt\nindex 9d4f151..21c7af2 100644\n--- a/Documentation/git-p4.txt\n+++ b/Documentation/git-p4.txt\n@@ -104,7 +104,7 @@ $ git p4 sync //path/in/your/perforce/depot\n ------------\n This imports the specified depot into\n 'refs/remotes/p4/master' in an existing Git repository.  The\n-'--branch' option can be used to specify a different branch to\n+`--branch` option can be used to specify a different branch to\n be used for the p4 content.\n \n If a Git repository includes branches 'refs/remotes/origin/p4', these\n@@ -114,7 +114,7 @@ from a Git remote, this can be useful in a multi-developer environment.\n \n If there are multiple branches, doing 'git p4 sync' will automatically\n use the \"BRANCH DETECTION\" algorithm to try to partition new changes\n-into the right branch.  This can be overridden with the '--branch'\n+into the right branch.  This can be overridden with the `--branch`\n option to specify just a single branch to update.\n \n \n@@ -150,10 +150,10 @@ $ git p4 submit topicbranch\n ------------\n \n The upstream reference is generally 'refs/remotes/p4/master', but can\n-be overridden using the '--origin=' command-line option.\n+be overridden using the `--origin=` command-line option.\n \n The p4 changes will be created as the user invoking 'git p4 submit'. The\n-'--preserve-user' option will cause ownership to be modified\n+`--preserve-user` option will cause ownership to be modified\n according to the author of the Git commit.  This option requires admin\n privileges in p4, which can be granted using 'p4 protect'.\n \n@@ -221,7 +221,7 @@ Git repository:\n \twhere they will be treated as remote-tracking branches by\n \tlinkgit:git-branch[1] and other commands.  This option instead\n \tputs p4 branches in 'refs/heads/p4/'.  Note that future\n-\tsync operations must specify '--import-local' as well so that\n+\tsync operations must specify `--import-local` as well so that\n \tthey can find the p4 branches in refs/heads.\n \n --max-changes <n>::\n@@ -245,7 +245,7 @@ Git repository:\n \tdefault, involves removing the entire depot path.  With this\n \toption, the full p4 depot path is retained in Git.  For example,\n \tpath '//depot/main/foo/bar.c', when imported from\n-\t'//depot/main/', becomes 'foo/bar.c'.  With '--keep-path', the\n+\t'//depot/main/', becomes 'foo/bar.c'.  With `--keep-path`, the\n \tGit path is instead 'depot/main/foo/bar.c'.\n \n --use-client-spec::\n@@ -341,7 +341,7 @@ p4 revision specifier on the end:\n     Import all changes from both named depot paths into a single\n     repository.  Only files below these directories are included.\n     There is not a subdirectory in Git for each \"proj1\" and \"proj2\".\n-    You must use the '--destination' option when specifying more\n+    You must use the `--destination` option when specifying more\n     than one depot path.  The revision specifier must be specified\n     identically on each depot path.  If there are files in the\n     depot paths with the same name, the path with the most recently\n@@ -355,7 +355,7 @@ CLIENT SPEC\n The p4 client specification is maintained with the 'p4 client' command\n and contains among other fields, a View that specifies how the depot\n is mapped into the client repository.  The 'clone' and 'sync' commands\n-can consult the client spec when given the '--use-client-spec' option or\n+can consult the client spec when given the `--use-client-spec` option or\n when the useClientSpec variable is true.  After 'git p4 clone', the\n useClientSpec variable is automatically set in the repository\n configuration file.  This allows future 'git p4 submit' commands to\n@@ -390,7 +390,7 @@ different areas in the tree, and indicate related content.  'git p4'\n can use these mappings to determine branch relationships.\n \n If you have a repository where all the branches of interest exist as\n-subdirectories of a single depot path, you can use '--detect-branches'\n+subdirectories of a single depot path, you can use `--detect-branches`\n when cloning or syncing to have 'git p4' automatically find\n subdirectories in p4, and to generate these as branches in Git.\n \n@@ -507,7 +507,7 @@ git-p4.labelImportRegexp::\n git-p4.useClientSpec::\n \tSpecify that the p4 client spec should be used to identify p4\n \tdepot paths of interest.  This is equivalent to specifying the\n-\toption '--use-client-spec'.  See the \"CLIENT SPEC\" section above.\n+\toption `--use-client-spec`.  See the \"CLIENT SPEC\" section above.\n \tThis variable is a boolean, not the name of a p4 client.\n \n git-p4.pathEncoding::\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 19f46b6..93c3527 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -275,7 +275,7 @@ origin +master` to force a push to the `master` branch). See the\n \tall submodules that changed in the revisions to be pushed will be\n \tpushed. If on-demand was not able to push all necessary revisions\n \tit will also be aborted and exit with non-zero status. A value of\n-\t'no' or using '--no-recurse-submodules' can be used to override the\n+\t'no' or using `--no-recurse-submodules` can be used to override the\n \tpush.recurseSubmodules configuration variable when no submodule\n \trecursion is required.\n \ndiff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\nindex 0387b40..de222c8 100644\n--- a/Documentation/git-rebase.txt\n+++ b/Documentation/git-rebase.txt\n@@ -208,10 +208,10 @@ rebase.stat::\n \trebase. False by default.\n \n rebase.autoSquash::\n-\tIf set to true enable '--autosquash' option by default.\n+\tIf set to true enable `--autosquash` option by default.\n \n rebase.autoStash::\n-\tIf set to true enable '--autostash' option by default.\n+\tIf set to true enable `--autostash` option by default.\n \n rebase.missingCommitsCheck::\n \tIf set to \"warn\", print warnings about removed commits in\n@@ -220,7 +220,7 @@ rebase.missingCommitsCheck::\n \tdone. \"ignore\" by default.\n \n rebase.instructionFormat::\n-\tCustom commit list format to use during an '--interactive' rebase.\n+\tCustom commit list format to use during an `--interactive` rebase.\n \n OPTIONS\n -------\n@@ -428,9 +428,9 @@ without an explicit `--interactive`.\n \t\"fixup! \" or \"squash! \" after the first, in case you referred to an\n \tearlier fixup/squash with `git commit --fixup/--squash`.\n +\n-This option is only valid when the '--interactive' option is used.\n+This option is only valid when the `--interactive` option is used.\n +\n-If the '--autosquash' option is enabled by default using the\n+If the `--autosquash` option is enabled by default using the\n configuration variable `rebase.autoSquash`, this option can be\n used to override and disable this setting.\n \ndiff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt\nindex 1d7ecea..577b969 100644\n--- a/Documentation/git-remote.txt\n+++ b/Documentation/git-remote.txt\n@@ -137,9 +137,9 @@ branches, adds to that list.\n Retrieves the URLs for a remote. Configurations for `insteadOf` and\n `pushInsteadOf` are expanded here. By default, only the first URL is listed.\n +\n-With '--push', push URLs are queried rather than fetch URLs.\n+With `--push`, push URLs are queried rather than fetch URLs.\n +\n-With '--all', all URLs for the remote will be listed.\n+With `--all`, all URLs for the remote will be listed.\n \n 'set-url'::\n \n@@ -147,11 +147,11 @@ Changes URLs for the remote. Sets first URL for remote <name> that matches\n regex <oldurl> (first URL if no <oldurl> is given) to <newurl>. If\n <oldurl> doesn't match any URL, an error occurs and nothing is changed.\n +\n-With '--push', push URLs are manipulated instead of fetch URLs.\n+With `--push`, push URLs are manipulated instead of fetch URLs.\n +\n-With '--add', instead of changing existing URLs, new URL is added.\n+With `--add`, instead of changing existing URLs, new URL is added.\n +\n-With '--delete', instead of changing existing URLs, all URLs matching\n+With `--delete`, instead of changing existing URLs, all URLs matching\n regex <url> are deleted for remote <name>.  Trying to delete all\n non-push URLs is an error.\n +\ndiff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\nindex 573616a..837707a 100644\n--- a/Documentation/git-revert.txt\n+++ b/Documentation/git-revert.txt\n@@ -24,7 +24,7 @@ from the HEAD commit).\n Note: 'git revert' is used to record some new commits to reverse the\n effect of some earlier commits (often only a faulty one).  If you want to\n throw away all uncommitted changes in your working directory, you\n-should see linkgit:git-reset[1], particularly the '--hard' option.  If\n+should see linkgit:git-reset[1], particularly the `--hard` option.  If\n you want to extract specific files as they were in another commit, you\n should see linkgit:git-checkout[1], specifically the `git checkout\n <commit> -- <filename>` syntax.  Take care with these alternatives as\n@@ -37,7 +37,7 @@ OPTIONS\n \tFor a more complete list of ways to spell commit names, see\n \tlinkgit:gitrevisions[7].\n \tSets of commits can also be given but no traversal is done by\n-\tdefault, see linkgit:git-rev-list[1] and its '--no-walk'\n+\tdefault, see linkgit:git-rev-list[1] and its `--no-walk`\n \toption.\n \n -e::\ndiff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt\nindex d0b38b4..642d0ef 100644\n--- a/Documentation/git-send-email.txt\n+++ b/Documentation/git-send-email.txt\n@@ -66,7 +66,7 @@ This option may be specified multiple times.\n \tInvoke a text editor (see GIT_EDITOR in linkgit:git-var[1])\n \tto edit an introductory message for the patch series.\n +\n-When '--compose' is used, git send-email will use the From, Subject, and\n+When `--compose` is used, git send-email will use the From, Subject, and\n In-Reply-To headers specified in the message. If the body of the message\n (what you type after the headers and a blank line) only contains blank\n (or Git: prefixed) lines, the summary won't be sent, but From, Subject,\n@@ -182,19 +182,19 @@ $ git send-email --smtp-auth=\"PLAIN LOGIN GSSAPI\" ...\n +\n If at least one of the specified mechanisms matches the ones advertised by the\n SMTP server and if it is supported by the utilized SASL library, the mechanism\n-is used for authentication. If neither 'sendemail.smtpAuth' nor '--smtp-auth'\n+is used for authentication. If neither 'sendemail.smtpAuth' nor `--smtp-auth`\n is specified, all mechanisms supported by the SASL library can be used.\n \n --smtp-pass[=<password>]::\n \tPassword for SMTP-AUTH. The argument is optional: If no\n \targument is specified, then the empty string is used as\n \tthe password. Default is the value of `sendemail.smtpPass`,\n-\thowever '--smtp-pass' always overrides this value.\n+\thowever `--smtp-pass` always overrides this value.\n +\n Furthermore, passwords need not be specified in configuration files\n or on the command line. If a username has been specified (with\n-'--smtp-user' or a `sendemail.smtpUser`), but no password has been\n-specified (with '--smtp-pass' or `sendemail.smtpPass`), then\n+`--smtp-user` or a `sendemail.smtpUser`), but no password has been\n+specified (with `--smtp-pass` or `sendemail.smtpPass`), then\n a password is obtained using 'git-credential'.\n \n --smtp-server=<host>::\n@@ -240,7 +240,7 @@ must be used for each option.\n \n --smtp-user=<user>::\n \tUsername for SMTP-AUTH. Default is the value of `sendemail.smtpUser`;\n-\tif a username is not specified (with '--smtp-user' or `sendemail.smtpUser`),\n+\tif a username is not specified (with `--smtp-user` or `sendemail.smtpUser`),\n \tthen authentication is not attempted.\n \n --smtp-debug=0|1::\n@@ -364,8 +364,8 @@ have been specified, in which case default to 'compose'.\n \n --[no-]format-patch::\n \tWhen an argument may be understood either as a reference or as a file name,\n-\tchoose to understand it as a format-patch argument ('--format-patch')\n-\tor as a file name ('--no-format-patch'). By default, when such a conflict\n+\tchoose to understand it as a format-patch argument (`--format-patch`)\n+\tor as a file name (`--no-format-patch`). By default, when such a conflict\n \toccurs, git send-email will fail.\n \n --quiet::\n@@ -382,7 +382,7 @@ have been specified, in which case default to 'compose'.\n --\n +\n Default is the value of `sendemail.validate`; if this is not set,\n-default to '--validate'.\n+default to `--validate`.\n \n --force::\n \tSend emails even if safety checks would prevent it.\n@@ -428,13 +428,13 @@ sendmail;;\n \n sendemail.multiEdit::\n \tIf true (default), a single editor instance will be spawned to edit\n-\tfiles you have to edit (patches when '--annotate' is used, and the\n-\tsummary when '--compose' is used). If false, files will be edited one\n+\tfiles you have to edit (patches when `--annotate` is used, and the\n+\tsummary when `--compose` is used). If false, files will be edited one\n \tafter the other, spawning a new editor each time.\n \n sendemail.confirm::\n \tSets the default for whether to confirm before sending. Must be\n-\tone of 'always', 'never', 'cc', 'compose', or 'auto'. See '--confirm'\n+\tone of 'always', 'never', 'cc', 'compose', or 'auto'. See `--confirm`\n \tin the previous section for the meaning of these values.\n \n EXAMPLE\ndiff --git a/Documentation/git-send-pack.txt b/Documentation/git-send-pack.txt\nindex 6aa91e8..a831dd0 100644\n--- a/Documentation/git-send-pack.txt\n+++ b/Documentation/git-send-pack.txt\n@@ -44,7 +44,7 @@ OPTIONS\n \toption, then the refs from stdin are processed after those\n \ton the command line.\n +\n-If '--stateless-rpc' is specified together with this option then\n+If `--stateless-rpc` is specified together with this option then\n the list of refs must be in packet format (pkt-line). Each ref must\n be in a separate packet, and the list must end with a flush packet.\n \n@@ -99,11 +99,11 @@ Specifying the Refs\n There are three ways to specify which refs to update on the\n remote end.\n \n-With '--all' flag, all refs that exist locally are transferred to\n+With `--all` flag, all refs that exist locally are transferred to\n the remote side.  You cannot specify any '<ref>' if you use\n this flag.\n \n-Without '--all' and without any '<ref>', the heads that exist\n+Without `--all` and without any '<ref>', the heads that exist\n both on the local side and on the remote side are updated.\n \n When one or more '<ref>' are specified explicitly (whether on the\n@@ -134,13 +134,13 @@ name. See linkgit:git-rev-parse[1].\n      exist in the set of remote refs; the ref matched <src>\n      locally is used as the name of the destination.\n \n-Without '--force', the <src> ref is stored at the remote only if\n+Without `--force`, the <src> ref is stored at the remote only if\n <dst> does not exist, or <dst> is a proper subset (i.e. an\n ancestor) of <src>.  This check, known as \"fast-forward check\",\n is performed in order to avoid accidentally overwriting the\n remote ref and lose other peoples' commits from there.\n \n-With '--force', the fast-forward check is disabled for all refs.\n+With `--force`, the fast-forward check is disabled for all refs.\n \n Optionally, a <ref> parameter can be prefixed with a plus '+' sign\n to disable the fast-forward check only on that ref.\ndiff --git a/Documentation/git-show-branch.txt b/Documentation/git-show-branch.txt\nindex b91d4e5..7818e0f 100644\n--- a/Documentation/git-show-branch.txt\n+++ b/Documentation/git-show-branch.txt\n@@ -60,7 +60,7 @@ OPTIONS\n         are shown before their parents).\n \n --date-order::\n-\tThis option is similar to '--topo-order' in the sense that no\n+\tThis option is similar to `--topo-order` in the sense that no\n \tparent comes before all of its children, but otherwise commits\n \tare ordered according to their commit date.\n \ndiff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt\nindex 3a32451..c0aa871 100644\n--- a/Documentation/git-show-ref.txt\n+++ b/Documentation/git-show-ref.txt\n@@ -60,7 +60,7 @@ OPTIONS\n \n \tEnable stricter reference checking by requiring an exact ref path.\n \tAside from returning an error code of 1, it will also print an error\n-\tmessage if '--quiet' was not specified.\n+\tmessage if `--quiet` was not specified.\n \n --abbrev[=<n>]::\n \n@@ -70,7 +70,7 @@ OPTIONS\n -q::\n --quiet::\n \n-\tDo not print any results to stdout. When combined with '--verify' this\n+\tDo not print any results to stdout. When combined with `--verify` this\n \tcan be used to silently check if a reference exists.\n \n --exclude-existing[=<pattern>]::\n@@ -134,7 +134,7 @@ use:\n This will show \"refs/heads/master\" but also \"refs/remote/other-repo/master\",\n if such references exists.\n \n-When using the '--verify' flag, the command requires an exact path:\n+When using the `--verify` flag, the command requires an exact path:\n \n -----------------------------------------------------------------------------\n \tgit show-ref --verify refs/heads/master\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 698a668..7e17cad 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -98,11 +98,11 @@ your Perl's Getopt::Long is < v2.37).\n --ignore-paths=<regex>;;\n \tWhen passed to 'init' or 'clone' this regular expression will\n \tbe preserved as a config key.  See 'fetch' for a description\n-\tof '--ignore-paths'.\n+\tof `--ignore-paths`.\n --include-paths=<regex>;;\n \tWhen passed to 'init' or 'clone' this regular expression will\n \tbe preserved as a config key.  See 'fetch' for a description\n-\tof '--include-paths'.\n+\tof `--include-paths`.\n --no-minimize-url;;\n \tWhen tracking multiple directories (using --stdlayout,\n \t--branches, or --tags options), git svn will attempt to connect\n@@ -110,7 +110,7 @@ your Perl's Getopt::Long is < v2.37).\n \trepository.  This default allows better tracking of history if\n \tentire projects are moved within a repository, but may cause\n \tissues on repositories where read access restrictions are in\n-\tplace.  Passing '--no-minimize-url' will allow git svn to\n+\tplace.  Passing `--no-minimize-url` will allow git svn to\n \taccept URLs as-is without attempting to connect to a higher\n \tlevel directory.  This option is off by default when only\n \tone URL/branch is tracked (it would do little good).\n@@ -141,7 +141,7 @@ the same local time zone.\n --ignore-paths=<regex>;;\n \tThis allows one to specify a Perl regular expression that will\n \tcause skipping of all matching paths from checkout from SVN.\n-\tThe '--ignore-paths' option should match for every 'fetch'\n+\tThe `--ignore-paths` option should match for every 'fetch'\n \t(including automatic fetches due to 'clone', 'dcommit',\n \t'rebase', etc) on a given repository.\n +\n@@ -170,10 +170,10 @@ Skip \"branches\" and \"tags\" of first level directories;;\n --include-paths=<regex>;;\n \tThis allows one to specify a Perl regular expression that will\n \tcause the inclusion of only matching paths from checkout from SVN.\n-\tThe '--include-paths' option should match for every 'fetch'\n+\tThe `--include-paths` option should match for every 'fetch'\n \t(including automatic fetches due to 'clone', 'dcommit',\n-\t'rebase', etc) on a given repository. '--ignore-paths' takes\n-\tprecedence over '--include-paths'.\n+\t'rebase', etc) on a given repository. `--ignore-paths` takes\n+\tprecedence over `--include-paths`.\n +\n [verse]\n config key: svn-remote.<name>.include-paths\n@@ -191,7 +191,7 @@ config key: svn-remote.<name>.include-paths\n \tor if a second argument is passed; it will create a directory\n \tand work within that.  It accepts all arguments that the\n \t'init' and 'fetch' commands accept; with the exception of\n-\t'--fetch-all' and '--parent'.  After a repository is cloned,\n+\t`--fetch-all` and `--parent`.  After a repository is cloned,\n \tthe 'fetch' command will be able to update revisions without\n \taffecting the working tree; and the 'rebase' command will be\n \table to update the working tree with the latest changes.\n@@ -216,7 +216,7 @@ it preserves linear history with 'git rebase' instead of\n 'git merge' for ease of dcommitting with 'git svn'.\n +\n This accepts all options that 'git svn fetch' and 'git rebase'\n-accept.  However, '--fetch-all' only fetches from the current\n+accept.  However, `--fetch-all` only fetches from the current\n [svn-remote], and not all [svn-remote] definitions.\n +\n Like 'git rebase'; this requires that the working tree be clean\n@@ -919,7 +919,7 @@ parent of the branch. However, it is possible that there is no suitable\n Git commit to serve as parent.  This will happen, among other reasons,\n if the SVN branch is a copy of a revision that was not fetched by 'git\n svn' (e.g. because it is an old revision that was skipped with\n-'--revision'), or if in SVN a directory was copied that is not tracked\n+`--revision`), or if in SVN a directory was copied that is not tracked\n by 'git svn' (such as a branch that is not tracked at all, or a\n subdirectory of a tracked branch). In these cases, 'git svn' will still\n create a Git branch, but instead of using an existing Git commit as the\n@@ -996,12 +996,12 @@ directories in the working copy.  While this is the easiest way to get a\n copy of a complete repository, for projects with many branches it will\n lead to a working copy many times larger than just the trunk. Thus for\n projects using the standard directory structure (trunk/branches/tags),\n-it is recommended to clone with option '--stdlayout'. If the project\n+it is recommended to clone with option `--stdlayout`. If the project\n uses a non-standard structure, and/or if branches and tags are not\n required, it is easiest to only clone one directory (typically trunk),\n without giving any repository layout options.  If the full history with\n-branches and tags is required, the options '--trunk' / '--branches' /\n-'--tags' must be used.\n+branches and tags is required, the options `--trunk` / `--branches` /\n+`--tags` must be used.\n \n When using multiple --branches or --tags, 'git svn' does not automatically\n handle name collisions (for example, if two branches from different paths have\ndiff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt\nindex 6b89393..3225d0e 100644\n--- a/Documentation/git-tag.txt\n+++ b/Documentation/git-tag.txt\n@@ -167,7 +167,7 @@ This option is only applicable when listing tags without annotation lines.\n \n --[no-]merged [<commit>]::\n \tOnly list tags whose tips are reachable, or not reachable\n-\tif '--no-merged' is used, from the specified commit ('HEAD'\n+\tif `--no-merged` is used, from the specified commit ('HEAD'\n \tif not specified).\n \n CONFIGURATION\ndiff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt\nindex c6cbed1..7386c93 100644\n--- a/Documentation/git-update-index.txt\n+++ b/Documentation/git-update-index.txt\n@@ -102,7 +102,7 @@ thus, in case the assumed-untracked file is changed upstream,\n you will need to handle the situation manually.\n \n --really-refresh::\n-\tLike '--refresh', but checks stat information unconditionally,\n+\tLike `--refresh`, but checks stat information unconditionally,\n \twithout regard to the \"assume unchanged\" setting.\n \n --[no-]skip-worktree::\n@@ -211,7 +211,7 @@ will remove the intended effect of the option.\n \n Using --refresh\n ---------------\n-'--refresh' does not calculate a new sha1 file or bring the index\n+`--refresh` does not calculate a new sha1 file or bring the index\n up-to-date for mode/content changes. But what it *does* do is to\n \"re-match\" the stat information of a file with the index, so that you\n can refresh the index for a file that hasn't been changed but where\n@@ -222,7 +222,7 @@ up the stat index details with the proper files.\n \n Using --cacheinfo or --info-only\n --------------------------------\n-'--cacheinfo' is used to register a file that is not in the\n+`--cacheinfo` is used to register a file that is not in the\n current working directory.  This is useful for minimum-checkout\n merging.\n \n@@ -232,12 +232,12 @@ To pretend you have a file with mode and sha1 at path, say:\n $ git update-index --cacheinfo <mode>,<sha1>,<path>\n ----------------\n \n-'--info-only' is used to register files without placing them in the object\n+`--info-only` is used to register files without placing them in the object\n database.  This is useful for status-only repositories.\n \n-Both '--cacheinfo' and '--info-only' behave similarly: the index is updated\n-but the object database isn't.  '--cacheinfo' is useful when the object is\n-in the database but the file isn't available locally.  '--info-only' is\n+Both `--cacheinfo` and `--info-only` behave similarly: the index is updated\n+but the object database isn't.  `--cacheinfo` is useful when the object is\n+in the database but the file isn't available locally.  `--info-only` is\n useful when the file is available, but you do not wish to update the\n object database.\n \ndiff --git a/Documentation/git-web--browse.txt b/Documentation/git-web--browse.txt\nindex 7daa28f..2d6b09a 100644\n--- a/Documentation/git-web--browse.txt\n+++ b/Documentation/git-web--browse.txt\n@@ -110,7 +110,7 @@ Note about git-config --global\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n Note that these configuration variables should probably be set using\n-the '--global' flag, for example like this:\n+the `--global` flag, for example like this:\n \n ------------------------------------------------\n $ git config --global web.browser firefox\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex b861087..0169e1e 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -513,7 +513,7 @@ OPTIONS\n \n --help::\n \tPrints the synopsis and a list of the most commonly used\n-\tcommands. If the option '--all' or `-a` is given then all\n+\tcommands. If the option `--all` or `-a` is given then all\n \tavailable commands are printed. If a Git command is named this\n \toption will bring up the manual page for that command.\n +\n@@ -855,16 +855,16 @@ Git so take care if using a foreign front-end.\n \tIf the `GIT_DIR` environment variable is set then it\n \tspecifies a path to use instead of the default `.git`\n \tfor the base of the repository.\n-\tThe '--git-dir' command-line option also sets this value.\n+\tThe `--git-dir` command-line option also sets this value.\n \n `GIT_WORK_TREE`::\n \tSet the path to the root of the working tree.\n-\tThis can also be controlled by the '--work-tree' command-line\n+\tThis can also be controlled by the `--work-tree` command-line\n \toption and the core.worktree configuration variable.\n \n `GIT_NAMESPACE`::\n \tSet the Git namespace; see linkgit:gitnamespaces[7] for details.\n-\tThe '--namespace' command-line option also sets this value.\n+\tThe `--namespace` command-line option also sets this value.\n \n `GIT_CEILING_DIRECTORIES`::\n \tThis should be a colon-separated list of absolute paths.  If\ndiff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\nindex 15b3bfa..4546fa0 100644\n--- a/Documentation/gitcore-tutorial.txt\n+++ b/Documentation/gitcore-tutorial.txt\n@@ -949,7 +949,7 @@ for details.\n [NOTE]\n If there were more commits on the 'master' branch after the merge, the\n merge commit itself would not be shown by 'git show-branch' by\n-default.  You would need to provide '--sparse' option to make the\n+default.  You would need to provide `--sparse` option to make the\n merge commit visible in this case.\n \n Now, let's pretend you are the one who did all the work in\ndiff --git a/Documentation/gitdiffcore.txt b/Documentation/gitdiffcore.txt\nindex c579593..08cf622 100644\n--- a/Documentation/gitdiffcore.txt\n+++ b/Documentation/gitdiffcore.txt\n@@ -28,8 +28,8 @@ The 'git diff-{asterisk}' family works by first comparing two sets of\n files:\n \n  - 'git diff-index' compares contents of a \"tree\" object and the\n-   working directory (when '--cached' flag is not used) or a\n-   \"tree\" object and the index file (when '--cached' flag is\n+   working directory (when `--cached` flag is not used) or a\n+   \"tree\" object and the index file (when `--cached` flag is\n    used);\n \n  - 'git diff-files' compares contents of the index file and the\ndiff --git a/Documentation/gitk.txt b/Documentation/gitk.txt\nindex 6ade002..a68d860 100644\n--- a/Documentation/gitk.txt\n+++ b/Documentation/gitk.txt\n@@ -82,7 +82,7 @@ linkgit:git-rev-list[1] for a complete list.\n \n --simplify-merges::\n \n-\tAdditional option to '--full-history' to remove some needless\n+\tAdditional option to `--full-history` to remove some needless\n \tmerges from the resulting history, as there are no selected\n \tcommits contributing to this merge.  (See \"History\n \tsimplification\" in linkgit:git-log[1] for a more detailed\ndiff --git a/Documentation/gitmodules.txt b/Documentation/gitmodules.txt\nindex ac70eca..07cdd73 100644\n--- a/Documentation/gitmodules.txt\n+++ b/Documentation/gitmodules.txt\n@@ -19,7 +19,7 @@ of linkgit:git-config[1].\n \n The file contains one subsection per submodule, and the subsection value\n is the name of the submodule. The name is set to the path where the\n-submodule has been added unless it was customized with the '--name'\n+submodule has been added unless it was customized with the `--name`\n option of 'git submodule add'. Each submodule section also contains the\n following required keys:\n \ndiff --git a/Documentation/gitremote-helpers.txt b/Documentation/gitremote-helpers.txt\nindex 1e86594..53ce1d0 100644\n--- a/Documentation/gitremote-helpers.txt\n+++ b/Documentation/gitremote-helpers.txt\n@@ -210,17 +210,17 @@ the remote repository.\n 'export-marks' <file>::\n \tThis modifies the 'export' capability, instructing Git to dump the\n \tinternal marks table to <file> when complete. For details,\n-\tread up on '--export-marks=<file>' in linkgit:git-fast-export[1].\n+\tread up on `--export-marks=<file>` in linkgit:git-fast-export[1].\n \n 'import-marks' <file>::\n \tThis modifies the 'export' capability, instructing Git to load the\n \tmarks specified in <file> before processing any input. For details,\n-\tread up on '--import-marks=<file>' in linkgit:git-fast-export[1].\n+\tread up on `--import-marks=<file>` in linkgit:git-fast-export[1].\n \n 'signed-tags'::\n \tThis modifies the 'export' capability, instructing Git to pass\n-\t'--signed-tags=verbatim' to linkgit:git-fast-export[1].  In the\n-\tabsence of this capability, Git will use '--signed-tags=warn-strip'.\n+\t`--signed-tags=verbatim` to linkgit:git-fast-export[1].  In the\n+\tabsence of this capability, Git will use `--signed-tags=warn-strip`.\n \n \n \ndiff --git a/Documentation/revisions.txt b/Documentation/revisions.txt\nindex 19314e3..15879b3 100644\n--- a/Documentation/revisions.txt\n+++ b/Documentation/revisions.txt\n@@ -71,7 +71,7 @@ some output processing may assume ref names in UTF-8.\n   existing log ('$GIT_DIR/logs/<ref>'). Note that this looks up the state\n   of your *local* ref at a given time; e.g., what was in your local\n   'master' branch last week. If you want to look at commits made during\n-  certain times, see '--since' and '--until'.\n+  certain times, see `--since` and `--until`.\n \n '<refname>@{<n>}', e.g. 'master@\\{1\\}'::\n   A ref followed by the suffix '@' with an ordinal specification\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290371","messageId":"20160628114015.25828-7-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 6/7] CodingGuidelines: formatting HEAD in documentation","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:14Z","receivedAt":"2016-06-28T11:42:13Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"The current practice is:\n\ngit/Documentation$ git grep \"'HEAD'\" | wc -l\n24\ngit/Documentation$ git grep \"\\`HEAD\\`\" | wc -l\n66\n\nLet's adopt the majority as a guideline.\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/CodingGuidelines | 5 +++--\n 1 file changed, 3 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\nindex 7f4769a..4cd95da 100644\n--- a/Documentation/CodingGuidelines\n+++ b/Documentation/CodingGuidelines\n@@ -527,12 +527,13 @@ Writing Documentation:\n  or commands:\n \n  Literal examples (e.g. use of command-line options, command names,\n- configuration and environment variables) must be typeset in monospace (i.e.\n- wrapped with backticks):\n+ branch names, configuration and environment variables) must be\n+ typeset in monospace (i.e. wrapped with backticks):\n    `--pretty=oneline`\n    `git rev-list`\n    `remote.pushDefault`\n    `GIT_DIR`\n+   `HEAD`\n \n  An environment variable must be prefixed with \"$\" only when referring to its\n  value and not when referring to the variable itself, in this case there is\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290372","messageId":"20160628114015.25828-3-Matthieu.Moy@imag.fr","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"[PATCH v2 2/7] doc: typeset short command-line options as literal","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2016-06-28T11:40:10Z","receivedAt":"2016-06-28T11:42:15Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"It was common in our documentation to surround short option names with\nforward quotes, which renders as italic in HTML. Instead, use backquotes\nwhich renders as monospace. This is one more step toward conformance to\nDocumentation/CodingGuidelines.\n\nThis was obtained with:\n\n  perl -pi -e \"s/'(-[a-z])'/\\`\\$1\\`/g\" *.txt\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n Documentation/config.txt              |  8 ++++----\n Documentation/diff-config.txt         |  2 +-\n Documentation/diff-format.txt         |  8 ++++----\n Documentation/diff-generate-patch.txt |  4 ++--\n Documentation/git-cat-file.txt        | 12 ++++++------\n Documentation/git-checkout.txt        |  4 ++--\n Documentation/git-clean.txt           |  2 +-\n Documentation/git-commit-tree.txt     |  2 +-\n Documentation/git-commit.txt          |  2 +-\n Documentation/git-cvsimport.txt       |  6 +++---\n Documentation/git-cvsserver.txt       |  8 ++++----\n Documentation/git-diff-tree.txt       | 14 +++++++-------\n Documentation/git-fetch-pack.txt      |  2 +-\n Documentation/git-filter-branch.txt   |  2 +-\n Documentation/git-grep.txt            |  2 +-\n Documentation/git-help.txt            |  4 ++--\n Documentation/git-ls-tree.txt         |  4 ++--\n Documentation/git-mktree.txt          |  2 +-\n Documentation/git-mv.txt              |  2 +-\n Documentation/git-notes.txt           |  2 +-\n Documentation/git-repack.txt          |  4 ++--\n Documentation/git-shell.txt           |  4 ++--\n Documentation/git.txt                 |  4 ++--\n 23 files changed, 52 insertions(+), 52 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 626243f..6d5e5ba 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -930,7 +930,7 @@ browser.<tool>.cmd::\n \n browser.<tool>.path::\n \tOverride the path for the given tool that may be used to\n-\tbrowse HTML help (see '-w' option in linkgit:git-help[1]) or a\n+\tbrowse HTML help (see `-w` option in linkgit:git-help[1]) or a\n \tworking repository in gitweb (see linkgit:git-instaweb[1]).\n \n clean.requireForce::\n@@ -1429,9 +1429,9 @@ gitcvs.logFile::\n \n gitcvs.usecrlfattr::\n \tIf true, the server will look up the end-of-line conversion\n-\tattributes for files to determine the '-k' modes to use. If\n+\tattributes for files to determine the `-k` modes to use. If\n \tthe attributes force Git to treat a file as text,\n-\tthe '-k' mode will be left blank so CVS clients will\n+\tthe `-k` mode will be left blank so CVS clients will\n \ttreat it as text. If they suppress text conversion, the file\n \twill be set with '-kb' mode, which suppresses any newline munging\n \tthe client might otherwise do. If the attributes do not allow\n@@ -1501,7 +1501,7 @@ gitweb.snapshot::\n \tSee linkgit:gitweb.conf[5] for description.\n \n grep.lineNumber::\n-\tIf set to true, enable '-n' option by default.\n+\tIf set to true, enable `-n` option by default.\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\ndiff --git a/Documentation/diff-config.txt b/Documentation/diff-config.txt\nindex f1101c7..d5a5b17 100644\n--- a/Documentation/diff-config.txt\n+++ b/Documentation/diff-config.txt\n@@ -105,7 +105,7 @@ diff.orderFile::\n \n diff.renameLimit::\n \tThe number of files to consider when performing the copy/rename\n-\tdetection; equivalent to the 'git diff' option '-l'.\n+\tdetection; equivalent to the 'git diff' option `-l`.\n \n diff.renames::\n \tWhether and how Git detects renames.  If set to \"false\",\ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\nindex 85b0890..f10fd54 100644\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -46,11 +46,11 @@ That is, from the left to the right:\n . sha1 for \"dst\"; 0\\{40\\} if creation, unmerged or \"look at work tree\".\n . a space.\n . status, followed by optional \"score\" number.\n-. a tab or a NUL when '-z' option is used.\n+. a tab or a NUL when `-z` option is used.\n . path for \"src\"\n-. a tab or a NUL when '-z' option is used; only exists for C or R.\n+. a tab or a NUL when `-z` option is used; only exists for C or R.\n . path for \"dst\"; only exists for C or R.\n-. an LF or a NUL when '-z' option is used, to terminate the record.\n+. an LF or a NUL when `-z` option is used, to terminate the record.\n \n Possible status letters are:\n \n@@ -86,7 +86,7 @@ diff format for merges\n ----------------------\n \n \"git-diff-tree\", \"git-diff-files\" and \"git-diff --raw\"\n-can take '-c' or '--cc' option\n+can take `-c` or '--cc' option\n to generate diff output also for merge commits.  The output differs\n from the format described above in the following way:\n \ndiff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt\nindex c91afee..18608f5 100644\n--- a/Documentation/diff-generate-patch.txt\n+++ b/Documentation/diff-generate-patch.txt\n@@ -2,7 +2,7 @@ Generating patches with -p\n --------------------------\n \n When \"git-diff-index\", \"git-diff-tree\", or \"git-diff-files\" are run\n-with a '-p' option, \"git diff\" without the '--raw' option, or\n+with a `-p` option, \"git diff\" without the '--raw' option, or\n \"git log\" with the \"-p\" option, they\n do not produce the output described above; instead they produce a\n patch file.  You can customize the creation of such patches via the\n@@ -114,7 +114,7 @@ index fabadb8,cc95eb0..4866510\n ------------\n \n 1.   It is preceded with a \"git diff\" header, that looks like\n-     this (when '-c' option is used):\n+     this (when `-c` option is used):\n \n        diff --combined file\n +\ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex eb3d694..f8d0dcf 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -15,8 +15,8 @@ SYNOPSIS\n DESCRIPTION\n -----------\n In its first form, the command provides the content or the type of an object in\n-the repository. The type is required unless '-t' or '-p' is used to find the\n-object type, or '-s' is used to find the object size, or '--textconv' is used\n+the repository. The type is required unless `-t` or `-p` is used to find the\n+object type, or `-s` is used to find the object size, or '--textconv' is used\n (which implies type \"blob\").\n \n In the second form, a list of objects (separated by linefeeds) is provided on\n@@ -144,13 +144,13 @@ respectively print:\n \n OUTPUT\n ------\n-If '-t' is specified, one of the <type>.\n+If `-t` is specified, one of the <type>.\n \n-If '-s' is specified, the size of the <object> in bytes.\n+If `-s` is specified, the size of the <object> in bytes.\n \n-If '-e' is specified, no output.\n+If `-e` is specified, no output.\n \n-If '-p' is specified, the contents of <object> are pretty-printed.\n+If `-p` is specified, the contents of <object> are pretty-printed.\n \n If <type> is specified, the raw (though uncompressed) contents of the <object>\n will be returned.\ndiff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\nindex 5e5273e..7a2201b 100644\n--- a/Documentation/git-checkout.txt\n+++ b/Documentation/git-checkout.txt\n@@ -157,7 +157,7 @@ of it\").\n \tWhen creating a new branch, set up \"upstream\" configuration. See\n \t\"--track\" in linkgit:git-branch[1] for details.\n +\n-If no '-b' option is given, the name of the new branch will be\n+If no `-b` option is given, the name of the new branch will be\n derived from the remote-tracking branch, by looking at the local part of\n the refspec configured for the corresponding remote, and then stripping\n the initial part up to the \"*\".\n@@ -165,7 +165,7 @@ This would tell us to use \"hack\" as the local branch when branching\n off of \"origin/hack\" (or \"remotes/origin/hack\", or even\n \"refs/remotes/origin/hack\").  If the given name has no slash, or the above\n guessing results in an empty name, the guessing is aborted.  You can\n-explicitly give a name with '-b' in such a case.\n+explicitly give a name with `-b` in such a case.\n \n --no-track::\n \tDo not set up \"upstream\" configuration, even if the\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 51a7e26..03056da 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -16,7 +16,7 @@ DESCRIPTION\n Cleans the working tree by recursively removing files that are not\n under version control, starting from the current directory.\n \n-Normally, only files unknown to Git are removed, but if the '-x'\n+Normally, only files unknown to Git are removed, but if the `-x`\n option is specified, ignored files are also removed. This can, for\n example, be useful to remove all build products.\n \ndiff --git a/Documentation/git-commit-tree.txt b/Documentation/git-commit-tree.txt\nindex cb69faa..002dae6 100644\n--- a/Documentation/git-commit-tree.txt\n+++ b/Documentation/git-commit-tree.txt\n@@ -44,7 +44,7 @@ OPTIONS\n \tAn existing tree object\n \n -p <parent>::\n-\tEach '-p' indicates the id of a parent commit object.\n+\tEach `-p` indicates the id of a parent commit object.\n \n -m <message>::\n \tA paragraph in the commit log message. This can be given more than\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex e704953..e295d49 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -75,7 +75,7 @@ OPTIONS\n \n -c <commit>::\n --reedit-message=<commit>::\n-\tLike '-C', but with '-c' the editor is invoked, so that\n+\tLike '-C', but with `-c` the editor is invoked, so that\n \tthe user can further edit the commit message.\n \n --fixup=<commit>::\ndiff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt\nindex 00a0679..bbf1c2b 100644\n--- a/Documentation/git-cvsimport.txt\n+++ b/Documentation/git-cvsimport.txt\n@@ -103,7 +103,7 @@ the old cvs2git tool.\n \n -p <options-for-cvsps>::\n \tAdditional options for cvsps.\n-\tThe options '-u' and '-A' are implicit and should not be used here.\n+\tThe options `-u` and '-A' are implicit and should not be used here.\n +\n If you need to pass multiple options, separate them with a comma.\n \n@@ -122,7 +122,7 @@ If you need to pass multiple options, separate them with a comma.\n \n -M <regex>::\n \tAttempt to detect merges based on the commit message with a custom\n-\tregex. It can be used with '-m' to enable the default regexes\n+\tregex. It can be used with `-m` to enable the default regexes\n \tas well. You must escape forward slashes.\n +\n The regex must capture the source branch name in $1.\n@@ -186,7 +186,7 @@ messages, bug-tracking systems, email archives, and the like.\n \n OUTPUT\n ------\n-If '-v' is specified, the script reports what it is doing.\n+If `-v` is specified, the script reports what it is doing.\n \n Otherwise, success is indicated the Unix way, i.e. by simply exiting with\n a zero exit status.\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex db4d7a9..5e3c6a8 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -402,12 +402,12 @@ Exports and tagging (tags and branches) are not supported at this stage.\n CRLF Line Ending Conversions\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n-By default the server leaves the '-k' mode blank for all files,\n+By default the server leaves the `-k` mode blank for all files,\n which causes the CVS client to treat them as a text files, subject\n to end-of-line conversion on some platforms.\n \n You can make the server use the end-of-line conversion attributes to\n-set the '-k' modes for files by setting the `gitcvs.usecrlfattr`\n+set the `-k` modes for files by setting the `gitcvs.usecrlfattr`\n config variable.  See linkgit:gitattributes[5] for more information\n about end-of-line conversion.\n \n@@ -415,9 +415,9 @@ Alternatively, if `gitcvs.usecrlfattr` config is not enabled\n or the attributes do not allow automatic detection for a filename, then\n the server uses the `gitcvs.allBinary` config for the default setting.\n If `gitcvs.allBinary` is set, then file not otherwise\n-specified will default to '-kb' mode. Otherwise the '-k' mode\n+specified will default to '-kb' mode. Otherwise the `-k` mode\n is left blank. But if `gitcvs.allBinary` is set to \"guess\", then\n-the correct '-k' mode will be guessed based on the contents of\n+the correct `-k` mode will be guessed based on the contents of\n the file.\n \n For best consistency with 'cvs', it is probably best to override the\ndiff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt\nindex 1439486..7558e49 100644\n--- a/Documentation/git-diff-tree.txt\n+++ b/Documentation/git-diff-tree.txt\n@@ -70,13 +70,13 @@ commits (but not trees).\n \tBy default, 'git diff-tree --stdin' does not show\n \tdifferences for merge commits.  With this flag, it shows\n \tdifferences to that commit from all of its parents. See\n-\talso '-c'.\n+\talso `-c`.\n \n -s::\n \tBy default, 'git diff-tree --stdin' shows differences,\n-\teither in machine-readable form (without '-p') or in patch\n-\tform (with '-p').  This output can be suppressed.  It is\n-\tonly useful with '-v' flag.\n+\teither in machine-readable form (without `-p`) or in patch\n+\tform (with `-p`).  This output can be suppressed.  It is\n+\tonly useful with `-v` flag.\n \n -v::\n \tThis flag causes 'git diff-tree --stdin' to also show\n@@ -94,14 +94,14 @@ include::pretty-options.txt[]\n \tone <tree-ish>, or '--stdin').  It shows the differences\n \tfrom each of the parents to the merge result simultaneously\n \tinstead of showing pairwise diff between a parent and the\n-\tresult one at a time (which is what the '-m' option does).\n+\tresult one at a time (which is what the `-m` option does).\n \tFurthermore, it lists only files which were modified\n \tfrom all parents.\n \n --cc::\n \tThis flag changes the way a merge commit patch is displayed,\n-\tin a similar way to the '-c' option. It implies the '-c'\n-\tand '-p' options and further compresses the patch output\n+\tin a similar way to the `-c` option. It implies the `-c`\n+\tand `-p` options and further compresses the patch output\n \tby omitting uninteresting hunks whose the contents in the parents\n \thave only two variants and the merge result picks one of them\n \twithout modification.  When all hunks are uninteresting, the commit\ndiff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt\nindex 239623c..4c8219d 100644\n--- a/Documentation/git-fetch-pack.txt\n+++ b/Documentation/git-fetch-pack.txt\n@@ -47,7 +47,7 @@ be in a separate packet, and the list must end with a flush packet.\n \n -q::\n --quiet::\n-\tPass '-q' flag to 'git unpack-objects'; this makes the\n+\tPass `-q` flag to 'git unpack-objects'; this makes the\n \tcloning process less verbose.\n \n -k::\ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex bd560d3..2d30297 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -52,7 +52,7 @@ if different from the rewritten ones, will be stored in the namespace\n \n Note that since this operation is very I/O expensive, it might\n be a good idea to redirect the temporary directory off-disk with the\n-'-d' option, e.g. on tmpfs.  Reportedly the speedup is very noticeable.\n+`-d` option, e.g. on tmpfs.  Reportedly the speedup is very noticeable.\n \n \n Filters\ndiff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt\nindex 40cfe37..557973b 100644\n--- a/Documentation/git-grep.txt\n+++ b/Documentation/git-grep.txt\n@@ -41,7 +41,7 @@ CONFIGURATION\n -------------\n \n grep.lineNumber::\n-\tIf set to true, enable '-n' option by default.\n+\tIf set to true, enable `-n` option by default.\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\ndiff --git a/Documentation/git-help.txt b/Documentation/git-help.txt\nindex 338b8d6..c6f7ce7 100644\n--- a/Documentation/git-help.txt\n+++ b/Documentation/git-help.txt\n@@ -18,10 +18,10 @@ With no options and no COMMAND or GUIDE given, the synopsis of the 'git'\n command and a list of the most commonly used Git commands are printed\n on the standard output.\n \n-If the option '--all' or '-a' is given, all available commands are\n+If the option '--all' or `-a` is given, all available commands are\n printed on the standard output.\n \n-If the option '--guide' or '-g' is given, a list of the useful\n+If the option '--guide' or `-g` is given, a list of the useful\n Git guides is also printed on the standard output.\n \n If a command, or a guide, is given, a manual page for that command or\ndiff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt\nindex 16e87fd..a9f1909 100644\n--- a/Documentation/git-ls-tree.txt\n+++ b/Documentation/git-ls-tree.txt\n@@ -20,7 +20,7 @@ in the current working directory.  Note that:\n \n  - the behaviour is slightly different from that of \"/bin/ls\" in that the\n    '<path>' denotes just a list of patterns to match, e.g. so specifying\n-   directory name (without '-r') will behave differently, and order of the\n+   directory name (without `-r`) will behave differently, and order of the\n    arguments does not matter.\n \n  - the behaviour is similar to that of \"/bin/ls\" in that the '<path>' is\n@@ -46,7 +46,7 @@ OPTIONS\n \n -t::\n \tShow tree entries even when going to recurse them. Has no effect\n-\tif '-r' was not passed. '-d' implies '-t'.\n+\tif `-r` was not passed. `-d` implies `-t`.\n \n -l::\n --long::\ndiff --git a/Documentation/git-mktree.txt b/Documentation/git-mktree.txt\nindex 5c6ebdf..c3616e7 100644\n--- a/Documentation/git-mktree.txt\n+++ b/Documentation/git-mktree.txt\n@@ -32,7 +32,7 @@ OPTIONS\n --batch::\n \tAllow building of more than one tree object before exiting.  Each\n \ttree is separated by as single blank line. The final new-line is\n-\toptional.  Note - if the '-z' option is used, lines are terminated\n+\toptional.  Note - if the `-z` option is used, lines are terminated\n \twith NUL.\n \n GIT\ndiff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt\nindex 6dcb8b2..79449bf 100644\n--- a/Documentation/git-mv.txt\n+++ b/Documentation/git-mv.txt\n@@ -35,7 +35,7 @@ OPTIONS\n \tSkip move or rename actions which would lead to an error\n \tcondition. An error happens when a source is neither existing nor\n \tcontrolled by Git, or when it would overwrite an existing\n-\tfile unless '-f' is given.\n+\tfile unless `-f` is given.\n -n::\n --dry-run::\n \tDo nothing; only show what would happen\ndiff --git a/Documentation/git-notes.txt b/Documentation/git-notes.txt\nindex 02a10bc..be7db30 100644\n--- a/Documentation/git-notes.txt\n+++ b/Documentation/git-notes.txt\n@@ -152,7 +152,7 @@ OPTIONS\n \n -c <object>::\n --reedit-message=<object>::\n-\tLike '-C', but with '-c' the editor is invoked, so that\n+\tLike '-C', but with `-c` the editor is invoked, so that\n \tthe user can further edit the note message.\n \n --allow-empty::\ndiff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt\nindex b9c02ce..0c03eec 100644\n--- a/Documentation/git-repack.txt\n+++ b/Documentation/git-repack.txt\n@@ -33,7 +33,7 @@ OPTIONS\n \tpack everything referenced into a single pack.\n \tEspecially useful when packing a repository that is used\n \tfor private development. Use\n-\twith '-d'.  This will clean up the objects that `git prune`\n+\twith `-d`.  This will clean up the objects that `git prune`\n \tleaves behind, but `git fsck --full --dangling` shows as\n \tdangling.\n +\n@@ -42,7 +42,7 @@ whole new pack in order to get any contained object, no matter how many\n other objects in that pack they already have locally.\n \n -A::\n-\tSame as `-a`, unless '-d' is used.  Then any unreachable\n+\tSame as `-a`, unless `-d` is used.  Then any unreachable\n \tobjects in a previous pack become loose, unpacked objects,\n \tinstead of being left in the old pack.  Unreachable objects\n \tare never intentionally added to a pack, even when repacking.\ndiff --git a/Documentation/git-shell.txt b/Documentation/git-shell.txt\nindex e4bdd22..2e30a3e 100644\n--- a/Documentation/git-shell.txt\n+++ b/Documentation/git-shell.txt\n@@ -24,7 +24,7 @@ named `git-shell-commands` in the user's home directory.\n COMMANDS\n --------\n \n-'git shell' accepts the following commands after the '-c' option:\n+'git shell' accepts the following commands after the `-c` option:\n \n 'git receive-pack <argument>'::\n 'git upload-pack <argument>'::\n@@ -43,7 +43,7 @@ directory.\n INTERACTIVE USE\n ---------------\n \n-By default, the commands above can be executed only with the '-c'\n+By default, the commands above can be executed only with the `-c`\n option; the shell is not interactive.\n \n If a `~/git-shell-commands` directory is present, 'git shell'\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex b0611ea..b861087 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -513,7 +513,7 @@ OPTIONS\n \n --help::\n \tPrints the synopsis and a list of the most commonly used\n-\tcommands. If the option '--all' or '-a' is given then all\n+\tcommands. If the option '--all' or `-a` is given then all\n \tavailable commands are printed. If a Git command is named this\n \toption will bring up the manual page for that command.\n +\n@@ -979,7 +979,7 @@ other\n \tThe command will be given exactly two or four arguments: the\n \t'username@host' (or just 'host') from the URL and the shell\n \tcommand to execute on that remote system, optionally preceded by\n-\t'-p' (literally) and the 'port' from the URL when it specifies\n+\t`-p` (literally) and the 'port' from the URL when it specifies\n \tsomething other than the default SSH port.\n +\n `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted\n-- \n2.8.2.397.gbe91ebf.dirty\n\n"},{"id":"290384","messageId":"xmqqmvm59w8d.fsf@gitster.mtv.corp.google.com","threadId":"42725","inReplyTo":"vpqr3bhzqej.fsf@anie.imag.fr","subject":"Re: [PATCH 2/6] doc: typeset long command-line options as literal","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-06-28T15:19:46Z","receivedAt":"2016-06-28T15:20:08Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:\n\n> Sorry, I forgot to mention when sending the series: this is to be\n> applied on top of tr/doc-tt (in next, marked \"will merge to master\").\n\nYup, I figured it out and these are queued there.  tr/doc-tt is part\nof 'master' now.\n"},{"id":"290565","messageId":"20160630064222.GD15380@sigill.intra.peff.net","threadId":"42725","inReplyTo":"20160628114015.25828-1-Matthieu.Moy@imag.fr","subject":"Re: [PATCH v2 0/7] literal formatting in documentation","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-30T06:42:22Z","receivedAt":"2016-06-30T06:42:51Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Jun 28, 2016 at 01:40:08PM +0200, Matthieu Moy wrote:\n\n> This should address all comments from Peff.\n\nThanks. The review is mind-numbing enough that I didn't do a complete\nread-through again, but just spot-checked a few places. This version\nlooks good to me.\n\n-Peff\n"}]}