{"thread":{"id":"27722","subject":"[PATCH] Documentation: quote double-dash in \" -- \" for AsciiDoc","startedAt":"2011-06-28T17:17:49Z","lastAt":"2011-06-29T16:44:31Z","messageCount":9,"participants":["Jonathan Nieder","Junio C Hamano","Jeff King","Ævar Arnfjörð Bjarmason"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"170634","messageId":"20110628171748.GA11485@elie","threadId":"27722","inReplyTo":null,"subject":"[PATCH] Documentation: quote double-dash in \" -- \" for AsciiDoc","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-06-28T17:17:49Z","receivedAt":"2011-06-28T17:17:49Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer\nAsciiDoc, 2010-08-23), outside of verbatim environments, newish\nversions of AsciiDoc will convert double hyphens to en dashes. Use\nthe litdd syntax introduced by that patch to avoid such misformatting\nin sentences where \"--\" represents the two-character \"end of options\"\nargument that separates revision names from filename patterns.\n\nSigned-off-by: Jonathan Nieder \n---\n Documentation/git-commit.txt | 2 +-\n Documentation/git-revert.txt | 2 +-\n 2 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex 7951cb7b..1764cf10 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -284,7 +284,7 @@ When recording your own work, the contents of modified files in\n your working tree are temporarily stored to a staging area\n called the \"index\" with 'git add'. A file can be\n reverted back, only in the index but not in the working tree,\n-to that of the last commit with `git reset HEAD -- `,\n+to that of the last commit with `git reset HEAD {litdd} `,\n which effectively reverts 'git add' and prevents the changes to\n this file from participating in the next commit. After building\n the state to be committed incrementally with these commands,\ndiff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\nindex ac10cfbb..a516d577 100644\n--- a/Documentation/git-revert.txt\n+++ b/Documentation/git-revert.txt\n@@ -23,7 +23,7 @@ throw away all uncommitted changes in your working directory, you\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- -- ` syntax. Take care with these alternatives as\n+ {litdd} ` syntax. Take care with these alternatives as\n both will discard uncommitted changes in your working directory.\n \n OPTIONS\n-- \n1.7.6.rc3\n"},{"id":"170643","messageId":"7vaad1tzve.fsf@alter.siamese.dyndns.org","threadId":"27722","inReplyTo":"20110628171748.GA11485@elie","subject":"Re: [PATCH] Documentation: quote double-dash in \" -- \" for AsciiDoc","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-06-28T21:22:45Z","receivedAt":"2011-06-28T21:22:45Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jonathan Nieder writes:\n\n> As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer\n> AsciiDoc, 2010-08-23), outside of verbatim environments, newish\n> versions of AsciiDoc will convert double hyphens to en dashes. Use\n> the litdd syntax introduced by that patch to avoid such misformatting\n> in sentences where \"--\" represents the two-character \"end of options\"\n> argument that separates revision names from filename patterns.\n\nThanks.\n\nThis looks very bad:\n\n $ cd $git/share/man\n $ grep -l '(em ' */*.?\n\neven though we do want em-dash for some hits in the above output. And\neven worse, there seem to be exceptions to this rule, like ...\n\n> diff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\n> index ac10cfbb..a516d577 100644\n> --- a/Documentation/git-revert.txt\n> +++ b/Documentation/git-revert.txt\n> @@ -23,7 +23,7 @@ throw away all uncommitted changes in your working directory, you\n> should see linkgit:git-reset[1], particularly the '--hard' option. If\n\n... the one before \"hard\" above.\n"},{"id":"170653","messageId":"20110628224717.GC4192@sigill.intra.peff.net","threadId":"27722","inReplyTo":"20110628171748.GA11485@elie","subject":"Re: [PATCH] Documentation: quote double-dash in \" -- \" for AsciiDoc","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2011-06-28T22:47:17Z","receivedAt":"2011-06-28T22:47:17Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Jun 28, 2011 at 12:17:49PM -0500, Jonathan Nieder wrote:\n\n> As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer\n> AsciiDoc, 2010-08-23), outside of verbatim environments, newish\n> versions of AsciiDoc will convert double hyphens to en dashes. Use\n> the litdd syntax introduced by that patch to avoid such misformatting\n> in sentences where \"--\" represents the two-character \"end of options\"\n> argument that separates revision names from filename patterns.\n\nUgh. I just did a similar thing for \"->\". I really wish asciidoc would\nnot expand symbols inside backticks in paragraph mode.\n\n> -to that of the last commit with `git reset HEAD -- `,\n> +to that of the last commit with `git reset HEAD {litdd} `,\n\nDoes \\-- work? That seems way more readable to me for people viewing the\nsource.\n\n-Peff\n"},{"id":"170657","messageId":"20110629041432.GA28690@elie","threadId":"27722","inReplyTo":"7vaad1tzve.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: quote double-dash in \" -- \" for AsciiDoc","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-06-29T04:15:07Z","receivedAt":"2011-06-29T04:15:07Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nJunio C Hamano wrote:\n\n> This looks very bad:\n> \n> $ cd $git/share/man\n> $ grep -l '(em ' */*.?\n>\n> even though we do want em-dash for some hits in the above output.\n\nTrue. Based on a glance at /usr/share/man, the patch misses:\n\n git-submodule.1: \"git submodule sync -- A\"\n various: git web--browse, git-mergetool--lib, git sh-i18n--envsubst\n rev-list options: history `A--P`\n\n> And\n> even worse, there seem to be exceptions to this rule, like ...\n>\n>> diff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\n>> index ac10cfbb..a516d577 100644\n>> --- a/Documentation/git-revert.txt\n>> +++ b/Documentation/git-revert.txt\n>> @@ -23,7 +23,7 @@ throw away all uncommitted changes in your working directory, you\n>> should see linkgit:git-reset[1], particularly the '--hard' option. If\n\nSloppy of me. For reference, here's the rule from asciidoc.conf.\n\n\t# -- Spaced and unspaced em dashes (entity reference —).\n\t# Space on both sides is translated to thin space characters.\n\t(^-- )=— \n\t(\\n-- )|( -- )|( --\\n)= — \n\t(\\w)--(\\w)=\\1—\\2\n\t\\\\--(?!-)=--\n\nSo:\n\n - \"\\--\" always represents two dashes, unless followed by another\n minus sign. There is no obvious technical reason to prefer {litdd}\n over \\-- or vice versa.\n\n - options like \"--hard\" are safe nowadays (though it's equally safe\n to escape them as \"\\--hard\"). Likewise, the trailing \"--\" in\n \"foo--\" is left unmolested.\n\n - before version 8.3.0[*], no unescaped \"--\" was safe for HTML output.\n They all would be converted to em dashes.\n\nWill prepare a new patch that takes care of the missed spots using \\--\nexcept in cases like \"git web{litdd}browse\", to roughly follow the\nexisting style. If someone wants to change those to \"git web\\--browse\"\nwith a patch on top, I won't mind.\n\nThanks, both.\n\nRegards,\nJonathan\n\n[*] Quick history:\n\n - asciidoc 8.4.1\n - [98be31f1] line 1 (^-- ) is added (\"Emdash replacement recognized at\n start of block\")\n - asciidoc 8.3.5\n - asciidoc 8.3.0\n - [6e71157d] line 3 ((\\w)--(\\w)) is introduced. It replaces the\n previous regex (\\n|[^-\\s\\\\])--([^-\\s]|\\n), which had been guarded by\n \"ifndef::doctype-manpage\" to mitigate the effect of false positives.\n - [46fbb7b7] The overeager pattern ([^\\n \\\\])--([^-\\s])=\\1—\\2\n guarded by \"ifdef::doctype-manpage\" is removed, since it has too\n many false positives (\"Allow unescaped -- option prefixes in man\n pages (was not working in all situations)\")\n - [12032332] Patterns start to capture surrounding whitespace so it\n can be converted to thin space. In this spirit, the second line\n ((\\n-- )|( -- )| --\\n)) is introduced, the pattern\n (^|[^-\\\\])--($|[^-]) guarded by \"ifndef::doctype-manpage\" changes\n to (\\n|[^-\\s\\\\])--([^-\\s]|\\n), and the pattern (^|\\s*[^\\S\\\\])--($|\\s+)\n guarded by \"ifdef::doctype-manpage\" changes to ([^\\n \\\\])--([^-\\s]).\n - asciidoc 8.2.7\n - asciidoc 8.2.4\n - asciidoc migrates from svn to mercurial (i.e., beginning of\n history).\n\nPre-history (from CHANGELOG.txt):\n\n - asciidoc 7.0.0: \"Manpage command names containing dashes (in the\n manpage NAME section) were misinterpreted as the spaced dash\n command name/purpose separator. Bug report and patch supplied by\n David Greaves\"\n - asciidoc 6.0.3: \"Spaced and unspaced em dashes are now recognized\n (previously only spaced em dashes were recognized).\"\n - asciidoc 5.0.6: \"A replacement has been added to `asciidoc.conf` to\n replace inline double dashes with the `—` entity.\"\n"},{"id":"170658","messageId":"20110629053133.GB28690@elie","threadId":"27722","inReplyTo":"20110628171748.GA11485@elie","subject":"[PATCH v2 0/2] Documentation: quote double-dash for AsciiDoc","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-06-29T05:31:33Z","receivedAt":"2011-06-29T05:31:33Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nThanks to Peff and Junio for comments. This version is split into two\npatches: the first applies to \"maint\", the second \"master\".\n\nJonathan Nieder (2):\n Documentation: quote double-dash for AsciiDoc\n Documentation/i18n: quote double-dash for AsciiDoc\n\n Documentation/config.txt | 2 +-\n Documentation/git-commit.txt | 2 +-\n Documentation/git-mergetool--lib.txt | 2 +-\n Documentation/git-revert.txt | 2 +-\n Documentation/git-sh-i18n--envsubst.txt | 6 +++---\n Documentation/git-sh-i18n.txt | 2 +-\n Documentation/git-submodule.txt | 2 +-\n Documentation/git-web--browse.txt | 2 +-\n Documentation/rev-list-options.txt | 2 +-\n 9 files changed, 11 insertions(+), 11 deletions(-)\n\n-- \n1.7.6\n"},{"id":"170659","messageId":"20110629053510.GC28690@elie","threadId":"27722","inReplyTo":"20110629053133.GB28690@elie","subject":"[PATCH 1/2 maint] Documentation: quote double-dash for AsciiDoc","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-06-29T05:35:10Z","receivedAt":"2011-06-29T05:35:10Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"AsciiDoc versions since 5.0.6 treat a double-dash surrounded by spaces\n(outside of verbatim environments) as a request to insert an em dash.\nSuch versions also treat the three-character sequence \"\\--\", when not\nfollowed by another dash, as a request to insert two literal minus\nsigns. Thus from time to time there have been patches to add\nbackslashes to AsciiDoc markup to escape double-dashes that are meant\nto be represent '--' characters used literally on the command line;\nsee v1.4.0-rc1~174, Fix up docs where \"--\" isn't displayed correctly,\n2006-05-05, for example.\n\nAsciiDoc 6.0.3 (2005-04-20) made life harder by also treating\ndouble-dashes without surrounding whitespace as markup for an em dash,\nthough only when formatting for backends other than the manpages\n(e.g., HTML). Many pages needed to be changed to use a backslash\nbefore the \"--\" in names of command-line flags like \"--add\" (see\nv0.99.6~37, Update tutorial, 2005-08-30).\n\nAsciiDoc 8.3.0 (2008-11-29) refined the em-dash rule to avoid that\nrequirement. Double-dashes without surrounding spaces are not\nrendered as em dashes any more unless bordered on both sides by\nalphanumeric characters. The unescaped markup for option names (e.g.,\n\"--add\") works fine, and many instances of this style have leaked into\nDocumentation/; git's HTML documentation contains many spurious em\ndashes when formatted by an older toolchain. (This patch will not\nchange that.)\n\nThe upshot: \"--\" as an isolated word and in phrases like \"git\nweb--browse\" must be escaped if it is not to be rendered as an em dash\nby current asciidoc. Use \"\\--\" to avoid such misformatting in\nsentences in which \"--\" represents a literal double-minus command line\nargument that separates options and revs from pathspecs, and use\n\"{litdd}\" in cases where the double-dash is embedded in the command\nname. The latter is just for consistency with v1.7.3-rc0~13^2 (Work\naround em-dash handling in newer AsciiDoc, 2010-08-23).\n\nList of lines to fix found by grepping manpages for \"(em\".\n\nSigned-off-by: Jonathan Nieder \nImproved-by: Junio C Hamano \nImproved-by: Jeff King \n---\nChanges since v1:\n\n - clearer description\n - using \"git checkout \\-- \" instead of litdd\n for easier reading (but still git-web{litdd}browse for consistency\n with existing markup)\n\nSimplifications to the above description would be very welcome.\n\n Documentation/config.txt | 2 +-\n Documentation/git-commit.txt | 2 +-\n Documentation/git-mergetool--lib.txt | 2 +-\n Documentation/git-revert.txt | 2 +-\n Documentation/git-submodule.txt | 2 +-\n Documentation/git-web--browse.txt | 2 +-\n Documentation/rev-list-options.txt | 2 +-\n 7 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex d1613621..4682fbbb 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -674,7 +674,7 @@ branch..rebase::\n browser..cmd::\n \tSpecify the command to invoke the specified browser. The\n \tspecified command is evaluated in shell with the URLs passed\n-\tas arguments. (See linkgit:git-web--browse[1].)\n+\tas arguments. (See linkgit:git-web{litdd}browse[1].)\n \n browser..path::\n \tOverride the path for the given tool that may be used to\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex d0534b8c..872cb04a 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -276,7 +276,7 @@ When recording your own work, the contents of modified files in\n your working tree are temporarily stored to a staging area\n called the \"index\" with 'git add'. A file can be\n reverted back, only in the index but not in the working tree,\n-to that of the last commit with `git reset HEAD -- `,\n+to that of the last commit with `git reset HEAD \\-- `,\n which effectively reverts 'git add' and prevents the changes to\n this file from participating in the next commit. After building\n the state to be committed incrementally with these commands,\ndiff --git a/Documentation/git-mergetool--lib.txt b/Documentation/git-mergetool--lib.txt\nindex 63ededec..5b0d51f7 100644\n--- a/Documentation/git-mergetool--lib.txt\n+++ b/Documentation/git-mergetool--lib.txt\n@@ -7,7 +7,7 @@ git-mergetool--lib - Common git merge tool shell scriptlets\n \n SYNOPSIS\n --------\n-'TOOL_MODE=(diff|merge) . \"$(git --exec-path)/git-mergetool--lib\"'\n+'TOOL_MODE=(diff|merge) . \"$(git --exec-path)/git-mergetool{litdd}lib\"'\n \n DESCRIPTION\n -----------\ndiff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\nindex ac10cfbb..6a21b37f 100644\n--- a/Documentation/git-revert.txt\n+++ b/Documentation/git-revert.txt\n@@ -23,7 +23,7 @@ throw away all uncommitted changes in your working directory, you\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- -- ` syntax. Take care with these alternatives as\n+ \\-- ` syntax. Take care with these alternatives as\n both will discard uncommitted changes in your working directory.\n \n OPTIONS\ndiff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt\nindex 1a16ff60..6ae6fd88 100644\n--- a/Documentation/git-submodule.txt\n+++ b/Documentation/git-submodule.txt\n@@ -172,7 +172,7 @@ sync::\n \trepositories accordingly.\n +\n \"git submodule sync\" synchronizes all submodules while\n-\"git submodule sync -- A\" synchronizes submodule \"A\" only.\n+\"git submodule sync \\-- A\" synchronizes submodule \"A\" only.\n \n OPTIONS\n -------\ndiff --git a/Documentation/git-web--browse.txt b/Documentation/git-web--browse.txt\nindex 69d92fa0..9b0d1fe3 100644\n--- a/Documentation/git-web--browse.txt\n+++ b/Documentation/git-web--browse.txt\n@@ -68,7 +68,7 @@ browser..path\n You can explicitly provide a full path to your preferred browser by\n setting the configuration variable 'browser..path'. For example,\n you can configure the absolute path to firefox by setting\n-'browser.firefox.path'. Otherwise, 'git web--browse' assumes the tool\n+'browser.firefox.path'. Otherwise, 'git web{litdd}browse' assumes the tool\n is available in PATH.\n \n browser..cmd\ndiff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt\nindex 73111bb0..5b29ad39 100644\n--- a/Documentation/rev-list-options.txt\n+++ b/Documentation/rev-list-options.txt\n@@ -309,7 +309,7 @@ that you are filtering for a file `foo` in this commit graph:\n \t \\ / / / /\n \t `-------------'\n -----------------------------------------------------------------------\n-The horizontal line of history A--P is taken to be the first parent of\n+The horizontal line of history A---P 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-- \n1.7.6\n"},{"id":"170660","messageId":"20110629053648.GD28690@elie","threadId":"27722","inReplyTo":"20110629053133.GB28690@elie","subject":"[PATCH 2/2] Documentation/i18n: quote double-dash for AsciiDoc","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-06-29T05:36:48Z","receivedAt":"2011-06-29T05:36:48Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer\nAsciiDoc, 2010-08-23), if double dashes in names of commands are not\nescaped, AsciiDoc renders them as em dashes.\n\nWhile fixing that, spell the command name as \"git sh-i18n--envsubst\"\n(2 words) instead of emphasizing the name of the binary (one\nhyphenated name) and format it in italics.\n\nSigned-off-by: Jonathan Nieder \n---\nThanks for reading.\n\n Documentation/git-sh-i18n--envsubst.txt | 6 +++---\n Documentation/git-sh-i18n.txt | 2 +-\n 2 files changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-sh-i18n--envsubst.txt b/Documentation/git-sh-i18n--envsubst.txt\nindex 61e4c08d..6e3a9539 100644\n--- a/Documentation/git-sh-i18n--envsubst.txt\n+++ b/Documentation/git-sh-i18n--envsubst.txt\n@@ -10,8 +10,8 @@ SYNOPSIS\n [verse]\n eval_gettext () {\n \tprintf \"%s\" \"$1\" | (\n-\t\texport PATH $('git sh-i18n--envsubst' --variables \"$1\");\n-\t\t'git sh-i18n--envsubst' \"$1\"\n+\t\texport PATH $('git sh-i18n{litdd}envsubst' --variables \"$1\");\n+\t\t'git sh-i18n{litdd}envsubst' \"$1\"\n \t)\n }\n \n@@ -22,7 +22,7 @@ This is not a command the end user would want to run. Ever.\n This documentation is meant for people who are studying the\n plumbing scripts and/or are writing new ones.\n \n-git-sh-i18n--envsubst is Git's stripped-down copy of the GNU\n+'git sh-i18n{litdd}envsubst' is Git's stripped-down copy of the GNU\n `envsubst(1)` program that comes with the GNU gettext package. It's\n used internally by linkgit:git-sh-i18n[1] to interpolate the variables\n passed to the the `eval_gettext` function.\ndiff --git a/Documentation/git-sh-i18n.txt b/Documentation/git-sh-i18n.txt\nindex 3b1f7ac7..eca69e3d 100644\n--- a/Documentation/git-sh-i18n.txt\n+++ b/Documentation/git-sh-i18n.txt\n@@ -34,7 +34,7 @@ gettext::\n eval_gettext::\n \tCurrently a dummy fall-through function implemented as a wrapper\n \taround `printf(1)` with variables expanded by the\n-\tlinkgit:git-sh-i18n--envsubst[1] helper. Will be replaced by a\n+\tlinkgit:git-sh-i18n{litdd}envsubst[1] helper. Will be replaced by a\n \treal gettext implementation in a later version.\n \n GIT\n-- \n1.7.6\n"},{"id":"170663","messageId":"BANLkTinRbw+mggfgP4s06jcn4SNzcE0byg@mail.gmail.com","threadId":"27722","inReplyTo":"20110629053648.GD28690@elie","subject":"Re: [PATCH 2/2] Documentation/i18n: quote double-dash for AsciiDoc","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2011-06-29T10:42:39Z","receivedAt":"2011-06-29T10:42:39Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Wed, Jun 29, 2011 at 07:36, Jonathan Nieder wrote:\n> As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer\n> AsciiDoc, 2010-08-23), if double dashes in names of commands are not\n> escaped, AsciiDoc renders them as em dashes.\n>\n> While fixing that, spell the command name as \"git sh-i18n--envsubst\"\n> (2 words) instead of emphasizing the name of the binary (one\n> hyphenated name) and format it in italics.\n\nThanks for fixing this, looks good to me.\n"},{"id":"170669","messageId":"20110629164431.GB20032@elie","threadId":"27722","inReplyTo":"20110629053648.GD28690@elie","subject":"[PATCH] fixup! Documentation/i18n: quote double-dash for AsciiDoc","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-06-29T16:44:31Z","receivedAt":"2011-06-29T16:44:31Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"The double-dash in the title should be escaped, too, to avoid spurious\nem dashes in the header:\n\n\t.TH \"GIT\\-SH\\-I18N\\(emENVSUB\" \"1\" \"06/26/2011\" \"Git 1\\&.7\\&.6\" \"Git Manual\"\n\nAsciiDoc 8.6.4 with DocBook XSL 1.76.0-RC1 copes fine and writes\n\"GIT\\-SH\\-I18N\\-\\-ENVSUB\" even without this change, which is why it\nwas missed before.\n\nSigned-off-by: Jonathan Nieder \n---\n Documentation/git-sh-i18n--envsubst.txt | 4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-sh-i18n--envsubst.txt b/Documentation/git-sh-i18n--envsubst.txt\nindex 6e3a9539..5c3ec327 100644\n--- a/Documentation/git-sh-i18n--envsubst.txt\n+++ b/Documentation/git-sh-i18n--envsubst.txt\n@@ -1,5 +1,5 @@\n-git-sh-i18n--envsubst(1)\n-========================\n+git-sh-i18n{litdd}envsubst(1)\n+=============================\n \n NAME\n ----\n-- \n1.7.6\n"}]}