{"thread":{"id":"20261","subject":"[PATCH] Documentation: Fix build failure of docs.","startedAt":"2009-07-28T15:38:49Z","lastAt":"2009-07-28T16:02:21Z","messageCount":2,"participants":["Saikiran Madugula","Thomas Rast"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"118968","messageId":"4A6F1B89.9080202@gmail.com","threadId":"20261","inReplyTo":null,"subject":"[PATCH] Documentation: Fix build failure of docs.","fromName":"Saikiran Madugula","fromEmail":"hummerbliss@gmail.com","sentAt":"2009-07-28T15:38:49Z","receivedAt":"2009-07-28T15:38:49Z","isPatch":true,"sender":{"key":"hummerbliss@gmail.com","avatar":null},"body":"This patch fixes the build failure due to what seems to be extraneous\ncharacters, \"+++\" in the git-filter-branch.txt file.\n\n$make man\n\n...\n\nASCIIDOC git-filter-branch.xml\n    XMLTO git-filter-branch.1\nxmlto: input does not validate (status 1)\n/home/bobthe/git.kernel.org/git/Documentation/git-filter-branch.xml:435:\nparser error : PCDATA invalid Char value 7\nClone it with <literal>git clone +++0+++</literal>.  The clone\n                                    ^\n/home/bobthe/git.kernel.org/git/Documentation/git-filter-branch.xml:435:\nparser error : PCDATA invalid Char value 7\nClone it with <literal>git clone +++0+++</literal>.  The clone\n                                      ^\nmake[1]: *** [git-filter-branch.1] Error 1\nmake[1]: Leaving directory\n`/home/bobthe/git.kernel.org/git/Documentation'\nmake: *** [man] Error 2\n\n...\n\nSigned-off-by: Saikiran Madugula <hummerbliss@gmail.com>\n---\n Documentation/git-filter-branch.txt |    2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt\nindex ab527b5..8a261c7 100644\n--- a/Documentation/git-filter-branch.txt\n+++ b/Documentation/git-filter-branch.txt\n@@ -364,7 +364,7 @@ objects until you tell it to.  First make sure that:\n Then there are two ways to get a smaller repository.  A safer way is\n to clone, that keeps your original intact.\n \n-* Clone it with `git clone +++file:///path/to/repo+++`.  The clone\n+* Clone it with `git clone file:///path/to/repo`.  The clone\n   will not have the removed objects.  See linkgit:git-clone[1].  (Note\n   that cloning with a plain path just hardlinks everything!)\n \n-- \n1.5.6.3\n"},{"id":"118969","messageId":"200907281802.23171.trast@student.ethz.ch","threadId":"20261","inReplyTo":"4A6F1B89.9080202@gmail.com","subject":"Re: [PATCH] Documentation: Fix build failure of docs.","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2009-07-28T16:02:21Z","receivedAt":"2009-07-28T16:02:21Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Saikiran Madugula wrote:\n> This patch fixes the build failure due to what seems to be extraneous\n> characters, \"+++\" in the git-filter-branch.txt file.\n[...]\n> ASCIIDOC git-filter-branch.xml\n>     XMLTO git-filter-branch.1\n> xmlto: input does not validate (status 1)\n> /home/bobthe/git.kernel.org/git/Documentation/git-filter-branch.xml:435:\n> parser error : PCDATA invalid Char value 7\n> Clone it with <literal>git clone +++0+++</literal>.  The clone\n\nNAK.  Presumably you are using an asciidoc 8.x?  Please check if\nsaying\n\n  make ASCIIDOC8=Yes man\n\nfixes the problem.  Read the comments in Documentation/Makefile for\nadvice on what precise combination of options you should use.  Also,\nif you do not want to actually work on docs\n\n  make quick-install-man\n\nis a much less painful way to get manpages (in this case, from Junio's\n'man' branch that has preformatted manpages for 'master').\n\nI put the +++ in there to stop the version I used at the time from\nrendering the closing backtick as part of the URL and garbling the\nentire paragraph in the process.  To be precise, with asciidoc 8.2.7\nand without the +++ I get\n\n  Clone it with <tt>git clone <a href=\"file:///path/to/repo</tt\">file:///path/to/repo</tt</a>>.\n\nin the HTML output.  Note the nested tags.  (With asciidoc 8.4.5 the\nproblem appears to be fixed.)\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"}]}