{"thread":{"id":"35328","subject":"[PATCH] Fix single quotes, AsciiDoc escaping, and other formatting/grammatical issues","startedAt":"2013-11-13T05:19:11Z","lastAt":"2013-11-13T17:51:25Z","messageCount":2,"participants":["Jason St. John","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"230550","messageId":"1384319951-31321-1-git-send-email-jstjohn@purdue.edu","threadId":"35328","inReplyTo":null,"subject":"[PATCH] Fix single quotes, AsciiDoc escaping, and other formatting/grammatical issues","fromName":"Jason St. John","fromEmail":"jstjohn@purdue.edu","sentAt":"2013-11-13T05:19:11Z","receivedAt":"2013-11-13T05:19:11Z","isPatch":true,"sender":{"key":"jstjohn@purdue.edu","avatar":"https://avatars.githubusercontent.com/u/1393510?v=4"},"body":"rev-list-options.txt:\n-- added line breaks before some \"endif\" AsciiDoc commands to fix syntax\n     highlighting in Vim\n-- added line breaks after some options subheadings to fix syntax\n     highlighting in Vim\n-- added backticks around options/commands that were missing it\n-- removed AsciiDoc escapes for \"--\" in options/commands\n-- replaced single quotes around options/commands with backticks\n-- replaced \"regexp\" with \"regular expression(s)\" where appropriate\n-- added backticks around a file path to /dev/null\n-- replaced some double quotes with proper AsciiDoc quotes (e.g.\n     ``foo'')\n-- slightly reworded some sentences for easier reading\n-- fix some typos (e.g. \"show\" -> \"shown\")\n\nSigned-off-by: Jason St. John <jstjohn@purdue.edu>\n---\nThis is a resubmit of patch 2/4 from my earlier patchset:\nhttp://marc.info/?l=git&m=138395814108214&w=2\n\n\n Documentation/rev-list-options.txt | 136 +++++++++++++++++++++----------------\n 1 file changed, 76 insertions(+), 60 deletions(-)\n\ndiff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt\nindex ec86d09..a7d2c5d 100644\n--- a/Documentation/rev-list-options.txt\n+++ b/Documentation/rev-list-options.txt\n@@ -40,6 +40,7 @@ ifdef::git-rev-list[]\n --min-age=<timestamp>::\n \n \tLimit the commits output to specified time range.\n+\n endif::git-rev-list[]\n \n --author=<pattern>::\n@@ -71,13 +72,15 @@ When `--show-notes` is in effect, the message from the notes as\n if it is part of the log message.\n \n --all-match::\n-\tLimit the commits output to ones that match all given --grep,\n+\n+\tLimit the commits output to ones that match all given `--grep`,\n \tinstead of ones that match at least one.\n \n -i::\n --regexp-ignore-case::\n \n-\tMatch the regexp limiting patterns without regard to letters case.\n+\tMatch the regular expression limiting patterns without regard to\n+\tletter case.\n \n --basic-regexp::\n \n@@ -98,7 +101,7 @@ if it is part of the log message.\n \n --perl-regexp::\n \n-\tConsider the limiting patterns to be Perl-compatible regexp.\n+\tConsider the limiting patterns to be Perl-compatible regular expressions.\n \tRequires libpcre to be compiled in.\n \n --remove-empty::\n@@ -129,6 +132,7 @@ again.  Equivalent forms are `--min-parents=0` (any commit has 0 or more\n parents) and `--max-parents=-1` (negative numbers denote no upper limit).\n \n --first-parent::\n+\n \tFollow only the first parent commit upon seeing a merge\n \tcommit.  This option can give a better overview when\n \tviewing the evolution of a particular topic branch,\n@@ -140,7 +144,7 @@ parents) and `--max-parents=-1` (negative numbers denote no upper limit).\n --not::\n \n \tReverses the meaning of the '{caret}' prefix (or lack thereof)\n-\tfor all following revision specifiers, up to the next '--not'.\n+\tfor all following revision specifiers, up to the next `--not`.\n \n --all::\n \n@@ -169,6 +173,7 @@ parents) and `--max-parents=-1` (negative numbers denote no upper limit).\n \tIf pattern lacks '?', '{asterisk}', or '[', '/{asterisk}' at the end is implied.\n \n --glob=<glob-pattern>::\n+\n \tPretend as if all the refs matching shell glob '<glob-pattern>'\n \tare listed on the command line as '<commit>'. Leading 'refs/',\n \tis automatically prepended if missing. If pattern lacks '?', '{asterisk}',\n@@ -186,6 +191,7 @@ ifndef::git-rev-list[]\n \twas listed and as if it was followed by `--not` and the good\n \tbisection refs `refs/bisect/good-*` on the command\n \tline.\n+\n endif::git-rev-list[]\n \n --stdin::\n@@ -202,7 +208,8 @@ ifdef::git-rev-list[]\n \tis primarily meant to allow the caller to\n \ttest the exit status to see if a range of objects is fully\n \tconnected (or not).  It is faster than redirecting stdout\n-\tto /dev/null as the output does not have to be formatted.\n+\tto `/dev/null` as the output does not have to be formatted.\n+\n endif::git-rev-list[]\n \n --cherry-mark::\n@@ -213,15 +220,15 @@ endif::git-rev-list[]\n --cherry-pick::\n \n \tOmit any commit that introduces the same change as\n-\tanother commit on the \"other side\" when the set of\n+\tanother commit on the ``other side'' when the set of\n \tcommits are limited with symmetric difference.\n +\n For example, if you have two branches, `A` and `B`, a usual way\n to list all commits on only one side of them is with\n `--left-right` (see the example below in the description of\n-the `--left-right` option).  It however shows the commits that were cherry-picked\n-from the other branch (for example, \"3rd on b\" may be cherry-picked\n-from branch A).  With this option, such pairs of commits are\n+the `--left-right` option). However, it shows the commits that were\n+cherry-picked from the other branch (for example, \"3rd on b\" may be\n+cherry-picked from branch A). With this option, such pairs of commits are\n excluded from the output.\n \n --left-only::\n@@ -254,14 +261,14 @@ list.\n \texclude (that is, '{caret}commit', 'commit1..commit2',\n \tnor 'commit1\\...commit2' notations cannot be used).\n +\n-With '\\--pretty' format other than oneline (for obvious reasons),\n+With `--pretty` format other than `oneline` (for obvious reasons),\n this causes the output to have two extra lines of information\n taken from the reflog.  By default, 'commit@\\{Nth}' notation is\n used in the output.  When the starting commit is specified as\n 'commit@\\{now}', output also uses 'commit@\\{timestamp}' notation\n-instead.  Under '\\--pretty=oneline', the commit message is\n+instead.  Under `--pretty=oneline`, the commit message is\n prefixed with this information on the same line.\n-This option cannot be combined with '\\--reverse'.\n+This option cannot be combined with `--reverse`.\n See also linkgit:git-reflog[1].\n \n --merge::\n@@ -320,7 +327,7 @@ Default mode::\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.\n \n@@ -352,36 +359,36 @@ The horizontal line of history A---Q is taken to be the first parent of\n each merge.  The commits are:\n \n * `I` is the initial commit, in which `foo` exists with contents\n-  \"asdf\", and a file `quux` exists with contents \"quux\".  Initial\n+  ``asdf'', and a file `quux` exists with contents ``quux''. Initial\n   commits are compared to an empty tree, so `I` is !TREESAME.\n \n-* In `A`, `foo` contains just \"foo\".\n+* In `A`, `foo` contains just ``foo''.\n \n * `B` contains the same change as `A`.  Its merge `M` is trivial and\n   hence TREESAME to all parents.\n \n-* `C` does not change `foo`, but its merge `N` changes it to \"foobar\",\n+* `C` does not change `foo`, but its merge `N` changes it to ``foobar'',\n   so it is not TREESAME to any parent.\n \n-* `D` sets `foo` to \"baz\".  Its merge `O` combines the strings from\n-  `N` and `D` to \"foobarbaz\"; i.e., it is not TREESAME to any parent.\n+* `D` sets `foo` to ``baz''. Its merge `O` combines the strings from\n+  `N` and `D` to ``foobarbaz''; i.e., it is not TREESAME to any parent.\n \n-* `E` changes `quux` to \"xyzzy\", and its merge `P` combines the\n-  strings to \"quux xyzzy\".  `P` is TREESAME to `O`, but not to `E`.\n+* `E` changes `quux` to ``xyzzy'', and its merge `P` combines the\n+  strings to ``quux xyzzy''. `P` is TREESAME to `O`, but not to `E`.\n \n * `X` is an independent root commit that added a new file `side`, and `Y`\n   modified it. `Y` is TREESAME to `X`. Its merge `Q` added `side` to `P`, and\n   `Q` is TREESAME to `P`, but not to `Y`.\n \n-'rev-list' walks backwards through history, including or excluding\n-commits based on whether '\\--full-history' and/or parent rewriting\n-(via '\\--parents' or '\\--children') are used.  The following settings\n+`rev-list` walks backwards through history, including or excluding\n+commits based on whether `--full-history` and/or parent rewriting\n+(via `--parents` or `--children`) are used.  The following settings\n are available.\n \n Default mode::\n \n \tCommits are included if they are not TREESAME to any parent\n-\t(though this can be changed, see '\\--sparse' below).  If the\n+\t(though this can be changed, see `--sparse` below).  If the\n \tcommit was a merge, and it was TREESAME to one parent, follow\n \tonly that parent.  (Even if there are several TREESAME\n \tparents, follow only one of them.)  Otherwise, follow all\n@@ -400,7 +407,7 @@ available, removed `B` from consideration entirely.  `C` was\n considered via `N`, but is TREESAME.  Root commits are compared to an\n empty tree, so `I` is !TREESAME.\n +\n-Parent/child relations are only visible with --parents, but that does\n+Parent/child relations are only visible with `--parents`, but that does\n not affect the commits selected in default mode, so we have shown the\n parent lines.\n \n@@ -427,7 +434,7 @@ them disconnected.\n --full-history with parent rewriting::\n \n \tOrdinary commits are only included if they are !TREESAME\n-\t(though this can be changed, see '\\--sparse' below).\n+\t(though this can be changed, see `--sparse` below).\n +\n Merges are always included.  However, their parent list is rewritten:\n Along each parent, prune away commits that are not included\n@@ -441,7 +448,7 @@ themselves.  This results in\n \t  `-------------'\n -----------------------------------------------------------------------\n +\n-Compare to '\\--full-history' without rewriting above.  Note that `E`\n+Compare to `--full-history` without rewriting above.  Note that `E`\n was pruned away because it is TREESAME, but the parent list of P was\n rewritten to contain `E`'s parent `I`.  The same happened for `C` and\n `N`, and `X`, `Y` and `Q`.\n@@ -458,14 +465,14 @@ affects inclusion:\n \n \tAll commits that are walked are included.\n +\n-Note that without '\\--full-history', this still simplifies merges: if\n+Note that without `--full-history`, this still simplifies merges: if\n one of the parents is TREESAME, we follow only that one, so the other\n sides of the merge are never walked.\n \n --simplify-merges::\n \n \tFirst, build a history graph in the same way that\n-\t'\\--full-history' with parent rewriting does (see above).\n+\t`--full-history` with parent rewriting does (see above).\n +\n Then simplify each commit `C` to its replacement `C'` in the final\n history according to the following rules:\n@@ -484,7 +491,7 @@ history according to the following rules:\n --\n +\n The effect of this is best shown by way of comparing to\n-'\\--full-history' with parent rewriting.  The example turns into:\n+`--full-history` with parent rewriting.  The example turns into:\n +\n -----------------------------------------------------------------------\n \t  .-A---M---N---O\n@@ -494,7 +501,7 @@ The effect of this is best shown by way of comparing to\n \t  `---------'\n -----------------------------------------------------------------------\n +\n-Note the major differences in `N`, `P` and `Q` over '--full-history':\n+Note the major differences in `N`, `P` and `Q` over `--full-history`:\n +\n --\n * `N`'s parent list had `I` removed, because it is an ancestor of the\n@@ -513,9 +520,9 @@ Finally, there is a fifth simplification mode available:\n --ancestry-path::\n \n \tLimit the displayed commits to those directly on the ancestry\n-\tchain between the \"from\" and \"to\" commits in the given commit\n-\trange. I.e. only display commits that are ancestor of the \"to\"\n-\tcommit, and descendants of the \"from\" commit.\n+\tchain between the ``from'' and ``to'' commits in the given commit\n+\trange. I.e. only display commits that are ancestor of the ``to''\n+\tcommit, and descendants of the ``from'' commit.\n +\n As an example use case, consider the following commit history:\n +\n@@ -530,14 +537,14 @@ As an example use case, consider the following commit history:\n A regular 'D..M' computes the set of commits that are ancestors of `M`,\n but excludes the ones that are ancestors of `D`. This is useful to see\n what happened to the history leading to `M` since `D`, in the sense\n-that \"what does `M` have that did not exist in `D`\". The result in this\n+that ``what does `M` have that did not exist in `D`''. The result in this\n example would be all the commits, except `A` and `B` (and `D` itself,\n of course).\n +\n When we want to find out what commits in `M` are contaminated with the\n bug introduced by `D` and need fixing, however, we might want to view\n only the subset of 'D..M' that are actually descendants of `D`, i.e.\n-excluding `C` and `K`. This is exactly what the '--ancestry-path'\n+excluding `C` and `K`. This is exactly what the `--ancestry-path`\n option does. Applied to the 'D..M' range, it results in:\n +\n -----------------------------------------------------------------------\n@@ -548,7 +555,7 @@ option does. Applied to the 'D..M' range, it results in:\n \t\t\t\tL--M\n -----------------------------------------------------------------------\n \n-The '\\--simplify-by-decoration' option allows you to view only the\n+The `--simplify-by-decoration` option allows you to view only the\n big picture of the topology of the history, by omitting commits\n that are not referenced by tags.  Commits are marked as !TREESAME\n (in other words, kept after history simplification rules described\n@@ -622,14 +629,17 @@ Commit Ordering\n By default, the commits are shown in reverse chronological order.\n \n --date-order::\n+\n \tShow no parents before all of its children are shown, but\n \totherwise show commits in the commit timestamp order.\n \n --author-date-order::\n+\n \tShow no parents before all of its children are shown, but\n \totherwise show commits in the author timestamp order.\n \n --topo-order::\n+\n \tShow no parents before all of its children are shown, and\n \tavoid showing commits on multiple lines of history\n \tintermixed.\n@@ -656,7 +666,7 @@ together.\n --reverse::\n \n \tOutput the commits in reverse order.\n-\tCannot be combined with '\\--walk-reflogs'.\n+\tCannot be combined with `--walk-reflogs`.\n \n Object Traversal\n ~~~~~~~~~~~~~~~~\n@@ -666,35 +676,35 @@ These options are mostly targeted for packing of Git repositories.\n --objects::\n \n \tPrint the object IDs of any object referenced by the listed\n-\tcommits.  '--objects foo ^bar' thus means \"send me\n+\tcommits.  `--objects foo ^bar` thus means ``send me\n \tall object IDs which I need to download if I have the commit\n-\tobject 'bar', but not 'foo'\".\n+\tobject _bar_ but not _foo_''.\n \n --objects-edge::\n \n-\tSimilar to '--objects', but also print the IDs of excluded\n-\tcommits prefixed with a \"-\" character.  This is used by\n-\tlinkgit:git-pack-objects[1] to build \"thin\" pack, which records\n+\tSimilar to `--objects`, but also print the IDs of excluded\n+\tcommits prefixed with a ``-'' character.  This is used by\n+\tlinkgit:git-pack-objects[1] to build ``thin'' pack, which records\n \tobjects in deltified form based on objects contained in these\n \texcluded commits to reduce network traffic.\n \n --unpacked::\n \n-\tOnly useful with '--objects'; print the object IDs that are not\n+\tOnly useful with `--objects`; print the object IDs that are not\n \tin packs.\n \n --no-walk[=(sorted|unsorted)]::\n \n \tOnly show the given commits, but do not traverse their ancestors.\n \tThis has no effect if a range is specified. If the argument\n-\t\"unsorted\" is given, the commits are show in the order they were\n+\t\"unsorted\" is given, the commits are shown in the order they were\n \tgiven on the command line. Otherwise (if \"sorted\" or no argument\n-\twas given), the commits are show in reverse chronological order\n+\twas given), the commits are shown in reverse chronological order\n \tby commit time.\n \n --do-walk::\n \n-\tOverrides a previous --no-walk.\n+\tOverrides a previous `--no-walk`.\n \n Commit Formatting\n ~~~~~~~~~~~~~~~~~\n@@ -714,20 +724,20 @@ include::pretty-options.txt[]\n --date=(relative|local|default|iso|rfc|short|raw)::\n \n \tOnly takes effect for dates shown in human-readable format, such\n-\tas when using \"--pretty\". `log.date` config variable sets a default\n-\tvalue for log command's --date option.\n+\tas when using `--pretty`. `log.date` config variable sets a default\n+\tvalue for the log command's `--date` option.\n +\n `--date=relative` shows dates relative to the current time,\n-e.g. \"2 hours ago\".\n+e.g. ``2 hours ago''.\n +\n `--date=local` shows timestamps in user's local time zone.\n +\n `--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format.\n +\n `--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822\n-format, often found in E-mail messages.\n+format, often found in e-mail messages.\n +\n-`--date=short` shows only date but not time, in `YYYY-MM-DD` format.\n+`--date=short` shows only the date, but not the time, in `YYYY-MM-DD` format.\n +\n `--date=raw` shows the date in the internal raw Git format `%s %z` format.\n +\n@@ -739,6 +749,7 @@ ifdef::git-rev-list[]\n \n \tPrint the contents of the commit in raw-format; each record is\n \tseparated with a NUL character.\n+\n endif::git-rev-list[]\n \n --parents::\n@@ -753,7 +764,9 @@ endif::git-rev-list[]\n \n ifdef::git-rev-list[]\n --timestamp::\n+\n \tPrint the raw commit timestamp.\n+\n endif::git-rev-list[]\n \n --left-right::\n@@ -795,18 +808,20 @@ you would get an output like this:\n +\n This enables parent rewriting, see 'History Simplification' below.\n +\n-This implies the '--topo-order' option by default, but the\n-'--date-order' option may also be specified.\n+This implies the `--topo-order` option by default, but the\n+`--date-order` option may also be specified.\n \n ifdef::git-rev-list[]\n --count::\n+\n \tPrint a number stating how many commits would have been\n \tlisted, and suppress all other output.  When used together\n-\twith '--left-right', instead print the counts for left and\n+\twith `--left-right`, instead print the counts for left and\n \tright commits, separated by a tab. When used together with\n-\t'--cherry-mark', omit patch equivalent commits from these\n+\t`--cherry-mark`, omit patch equivalent commits from these\n \tcounts and print the count for equivalent commits separated\n \tby a tab.\n+\n endif::git-rev-list[]\n \n \n@@ -814,7 +829,7 @@ ifndef::git-rev-list[]\n Diff Formatting\n ~~~~~~~~~~~~~~~\n \n-Below are listed options that control the formatting of diff output.\n+Listed below are options that control the formatting of diff output.\n Some of them are specific to linkgit:git-rev-list[1], however other diff\n options may be given. See linkgit:git-diff-files[1] for more options.\n \n@@ -828,7 +843,7 @@ options may be given. See linkgit:git-diff-files[1] for more options.\n \n --cc::\n \n-\tThis flag implies the '-c' option and further compresses the\n+\tThis flag implies the `-c` option and further compresses the\n \tpatch output by omitting uninteresting hunks whose contents in\n \tthe parents have only two variants and the merge result picks\n \tone of them without modification.\n@@ -838,7 +853,7 @@ options may be given. See linkgit:git-diff-files[1] for more options.\n \tThis flag makes the merge commits show the full diff like\n \tregular commits; for each merge parent, a separate log entry\n \tand diff is generated. An exception is that only diff against\n-\tthe first parent is shown when '--first-parent' option is given;\n+\tthe first parent is shown when `--first-parent` option is given;\n \tin that case, the output represents the changes the merge\n \tbrought _into_ the then-current branch.\n \n@@ -848,5 +863,6 @@ options may be given. See linkgit:git-diff-files[1] for more options.\n \n -t::\n \n-\tShow the tree objects in the diff output. This implies '-r'.\n+\tShow the tree objects in the diff output. This implies `-r`.\n+\n endif::git-rev-list[]\n-- \n1.8.4.2\n"},{"id":"230570","messageId":"xmqqtxfgdwbm.fsf@gitster.dls.corp.google.com","threadId":"35328","inReplyTo":"1384319951-31321-1-git-send-email-jstjohn@purdue.edu","subject":"Re: [PATCH] Fix single quotes, AsciiDoc escaping, and other formatting/grammatical issues","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-11-13T17:51:25Z","receivedAt":"2013-11-13T17:51:25Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Jason St. John\" <jstjohn@purdue.edu> writes:\n\n> rev-list-options.txt:\n> -- added line breaks before some \"endif\" AsciiDoc commands to fix syntax\n>      highlighting in Vim\n> -- added line breaks after some options subheadings to fix syntax\n>      highlighting in Vim\n\nCan't Vim be fixed instead (just kidding ;-)?\n\n> -- added backticks around options/commands that were missing it\n\n> -- removed AsciiDoc escapes for \"--\" in options/commands\n> -- replaced single quotes around options/commands with backticks\n\nI think the former is part of the latter. Both are good changes.\n\n> -- replaced \"regexp\" with \"regular expression(s)\" where appropriate\n\nGood.\n\n> -- added backticks around a file path to /dev/null\n\nGood---this is a mere special case of \"literal examples\" and can be\nthrown into the same bin as \"options, commands etc.\".\n\n> -- replaced some double quotes with proper AsciiDoc quotes (e.g.\n>      ``foo'')\n\nHmph.  No strong opinions either way from me, but others may have some.\n\n> -- slightly reworded some sentences for easier reading\n> -- fix some typos (e.g. \"show\" -> \"shown\")\n\nUsually, these two are better done in a patch separate from the\nformatting changes, but let's see how bad they are.\n\nInterestingly, only the last bullet point is in the imperative mood,\nthat gives an order to the codebase to \"be so\"; all others are\nwritten in past tense with implied subject \"I\".  We prefer to see\nthe former, i.e.\n\n        Subject: Documentation/rev-list-options: fix mark-ups and typos\n\n        Various fixes:\n\n         - Add an empty line before endif; this helps syntax\n           highlighting in Vim;\n\n         - Add an empty line after the item label line in labeled\n           lists; this helps syntax highlighting in Vim and also\n           helps line-rewrapping of the body text in Emacs;\n\n         - Typeset literal options, commands and pathnames in\n           monospace;\n\n         - Use \"regular expression(s)\" instead of \"regexp\" where\n           appropriate;\n\n         ...\n\n>\n> Signed-off-by: Jason St. John <jstjohn@purdue.edu>\n> ---\n> This is a resubmit of patch 2/4 from my earlier patchset:\n> http://marc.info/?l=git&m=138395814108214&w=2\n\nThanks.\n\n> @@ -213,15 +220,15 @@ endif::git-rev-list[]\n>  --cherry-pick::\n>  \n>  \tOmit any commit that introduces the same change as\n> -\tanother commit on the \"other side\" when the set of\n> +\tanother commit on the ``other side'' when the set of\n>  \tcommits are limited with symmetric difference.\n>  +\n>  For example, if you have two branches, `A` and `B`, a usual way\n>  to list all commits on only one side of them is with\n>  `--left-right` (see the example below in the description of\n\n> -the `--left-right` option).  It however shows the commits that were cherry-picked\n> -from the other branch (for example, \"3rd on b\" may be cherry-picked\n> -from branch A).  With this option, such pairs of commits are\n> +the `--left-right` option). However, it shows the commits that were\n> +cherry-picked from the other branch (for example, \"3rd on b\" may be\n> +cherry-picked from branch A). With this option, such pairs of commits are\n>  excluded from the output.\n\nI am not sure if I see improvement here.\n\nYou left \"3rd on b\" as-is---intended?\n\n> @@ -254,14 +261,14 @@ list.\n>  \texclude (that is, '{caret}commit', 'commit1..commit2',\n>  \tnor 'commit1\\...commit2' notations cannot be used).\n>  +\n> -With '\\--pretty' format other than oneline (for obvious reasons),\n> +With `--pretty` format other than `oneline` (for obvious reasons),\n\nGood eyes.  `oneline` is a literal value for an option that needs to\nbe in monospace.  Good.\n\n>  --no-walk[=(sorted|unsorted)]::\n>  \n>  \tOnly show the given commits, but do not traverse their ancestors.\n>  \tThis has no effect if a range is specified. If the argument\n> -\t\"unsorted\" is given, the commits are show in the order they were\n> +\t\"unsorted\" is given, the commits are shown in the order they were\n\nNot `unsorted`???\n\n>  \tgiven on the command line. Otherwise (if \"sorted\" or no argument\n\nLikewise.  Not `sorted`???\n\n>  `--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822\n> -format, often found in E-mail messages.\n> +format, often found in e-mail messages.\n\nHmph.  I do not have strong preference either way.\n\n> -`--date=short` shows only date but not time, in `YYYY-MM-DD` format.\n> +`--date=short` shows only the date, but not the time, in `YYYY-MM-DD` format.\n\nThanks.\n\n> @@ -814,7 +829,7 @@ ifndef::git-rev-list[]\n>  Diff Formatting\n>  ~~~~~~~~~~~~~~~\n>  \n> -Below are listed options that control the formatting of diff output.\n> +Listed below are options that control the formatting of diff output.\n\nGood.  This grammo dates back to Sep 2006 ;-)\n\nWill queue it as-is for now (primarily for me not to forget about\nthe topic), but we may want to further tweak some.\n\nThanks.\n"}]}