{"thread":{"id":"11417","subject":"generated HTML contains broken links","startedAt":"2007-12-28T23:49:31Z","lastAt":"2008-01-04T06:11:41Z","messageCount":9,"participants":["Eric Hanchrow","Dan McGee","Miklos Vajna","Junio C Hamano","Yannick Gingras"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"64166","messageId":"87sl1mqt10.fsf@offby1.atm01.sea.blarg.net","threadId":"11417","inReplyTo":null,"subject":"generated HTML contains broken links","fromName":"Eric Hanchrow","fromEmail":"offby1@blarg.net","sentAt":"2007-12-28T23:49:31Z","receivedAt":"2007-12-28T23:49:31Z","isPatch":false,"sender":{"key":"eric.hanchrow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3145?v=4"},"body":"I'm just starting to play with git, and have checked it out (with \"git\nclone git://git.kernel.org/pub/scm/git/git.git\"), and built the\ndocumentation (cd Documentation; make), on Cygwin.  I notice that the\ngenerated HTML docs are full of broken links -- for example, my file\nC:/cygwin/usr/local/src/git/Documentation/git.html includes this:\n\n        git<a href=\"git-instaweb\">1</a>\n\nbut there is no document named \"git-instaweb\" on my disk; instead,\nit's named \"git-instaweb.html\".\n\nI'm using asciidoc version 8.2.4, if it matters.\n-- \nI write [from 5 AM to 7 AM] to discover what I think.  After\nall, the bars aren't open that early.\n        -- Daniel Boorstin, former Librarian of Congress\n"},{"id":"64167","messageId":"4775B87D.4010507@gmail.com","threadId":"11417","inReplyTo":"87sl1mqt10.fsf@offby1.atm01.sea.blarg.net","subject":"Re: generated HTML contains broken links","fromName":"Dan McGee","fromEmail":"dpmcgee@gmail.com","sentAt":"2007-12-29T03:01:17Z","receivedAt":"2007-12-29T03:01:17Z","isPatch":false,"sender":{"key":"dpmcgee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/265817?v=4"},"body":"On 12/28/2007 05:49 PM, Eric Hanchrow wrote:\n> I'm just starting to play with git, and have checked it out (with \"git\n> clone git://git.kernel.org/pub/scm/git/git.git\"), and built the\n> documentation (cd Documentation; make), on Cygwin.  I notice that the\n> generated HTML docs are full of broken links -- for example, my file\n> C:/cygwin/usr/local/src/git/Documentation/git.html includes this:\n> \n>         git<a href=\"git-instaweb\">1</a>\n> \n> but there is no document named \"git-instaweb\" on my disk; instead,\n> it's named \"git-instaweb.html\".\n> \n> I'm using asciidoc version 8.2.4, if it matters.\n\nWe noticed this with the upgrade from Asciidoc 8.2.2 -> 8.2.3 on our project. It is broken in both the manpages and the HTML generated documentation. I've included an example below. So far, I haven't had luck tracking down the reason but I am looking into trying to fix this tonight. If anyone else is better with this stuff, it would be great if you could take a look.\n\nRelevant email on the pacman-dev list [1]:\n\nOn Nov 9, 2007 4:05 PM, Andrew Fyfe <andrew@neptune-one.net> wrote:\n> Did little digging, the breakage/change is in now asciidoc converts from asciidoc to xml (so it's \n> not docbook-xsl). In 8.2.2 manlink:pacman.conf[5] expands to\n> \n> <citerefentry><refentrytitle>pacman.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,\n> \n> in 8.2.3 it expands to\n> \n> man<ulink url=\"pacman.conf\">5</ulink>,\n\nNote that manlink is basically just a renamed gitlink, and can be found here:\n<http://projects.archlinux.org/git/?p=pacman.git;a=blob;f=doc/asciidoc.conf>\n\n-Dan\n\n[1] <http://archlinux.org/pipermail/pacman-dev/2007-November/009937.html>\n\n\n\nGenerated man pages from Junio:\nHOOKS\n       This command can run commit-msg, pre-commit, and post-commit hooks. See\n       [1]hooks for more information.\n\nSEE ALSO\n       git-add(1), git-rm(1), git-mv(1), git-merge(1), git-commit-tree(1)\n\nAUTHOR\n       Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano\n       <junkio@cox.net>\n\nGIT\n       Part of the git(7) suite\n\nMan pages generated locally (with Asciidoc 8.2.3 or 8.2.5):\nHOOKS\n       This command can run commit-msg, pre-commit, and post-commit hooks. See\n       hooks[5] for more information.\n\nSEE ALSO\n       git1[1], git1[2], git1[8], git1[6], git1[9]\n\nAUTHOR\n       Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano\n       <junkio@cox.net>\n\nGIT\n       Part of the git7[10] suite\n"},{"id":"64177","messageId":"20071229155705.GA23659@genesis.frugalware.org","threadId":"11417","inReplyTo":"4775B87D.4010507@gmail.com","subject":"Re: generated HTML contains broken links","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-12-29T15:57:05Z","receivedAt":"2007-12-29T15:57:05Z","isPatch":false,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Fri, Dec 28, 2007 at 09:01:17PM -0600, Dan McGee <dpmcgee@gmail.com> wrote:\n> Generated man pages from Junio:\n> HOOKS\n>        This command can run commit-msg, pre-commit, and post-commit hooks. See\n>        [1]hooks for more information.\n> \n> SEE ALSO\n>        git-add(1), git-rm(1), git-mv(1), git-merge(1), git-commit-tree(1)\n> \n> AUTHOR\n>        Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano\n>        <junkio@cox.net>\n> \n> GIT\n>        Part of the git(7) suite\n> \n> Man pages generated locally (with Asciidoc 8.2.3 or 8.2.5):\n> HOOKS\n>        This command can run commit-msg, pre-commit, and post-commit hooks. See\n>        hooks[5] for more information.\n> \n> SEE ALSO\n>        git1[1], git1[2], git1[8], git1[6], git1[9]\n> \n> AUTHOR\n>        Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano\n>        <junkio@cox.net>\n> \n> GIT\n>        Part of the git7[10] suite\n\nhttp://code.toofishes.net/gitweb.cgi?p=pacman.git;a=commitdiff;h=b3c6bdda38f7e370e1f80f02a61f1d3f08c1b57d\n\nhere is the commit that fixed the problem for pacman. what do you think,\nshould we rename gitlink to something else, too - or should we contact\nupstream to notify them about they caused a breakage?\n\nthanks,\n- VMiklos\n"},{"id":"64178","messageId":"449c10960712290824yd2c5783l8d0ba91bbad95789@mail.gmail.com","threadId":"11417","inReplyTo":"20071229155705.GA23659@genesis.frugalware.org","subject":"Re: generated HTML contains broken links","fromName":"Dan McGee","fromEmail":"dpmcgee@gmail.com","sentAt":"2007-12-29T16:24:58Z","receivedAt":"2007-12-29T16:24:58Z","isPatch":false,"sender":{"key":"dpmcgee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/265817?v=4"},"body":"On Dec 29, 2007 9:57 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:\n> On Fri, Dec 28, 2007 at 09:01:17PM -0600, Dan McGee <dpmcgee@gmail.com> wrote:\n> > Generated man pages from Junio:\n> > HOOKS\n> >        This command can run commit-msg, pre-commit, and post-commit hooks. See\n> >        [1]hooks for more information.\n> >\n> > SEE ALSO\n> >        git-add(1), git-rm(1), git-mv(1), git-merge(1), git-commit-tree(1)\n> >\n> > AUTHOR\n> >        Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano\n> >        <junkio@cox.net>\n> >\n> > GIT\n> >        Part of the git(7) suite\n> >\n> > Man pages generated locally (with Asciidoc 8.2.3 or 8.2.5):\n> > HOOKS\n> >        This command can run commit-msg, pre-commit, and post-commit hooks. See\n> >        hooks[5] for more information.\n> >\n> > SEE ALSO\n> >        git1[1], git1[2], git1[8], git1[6], git1[9]\n> >\n> > AUTHOR\n> >        Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano\n> >        <junkio@cox.net>\n> >\n> > GIT\n> >        Part of the git7[10] suite\n>\n> http://code.toofishes.net/gitweb.cgi?p=pacman.git;a=commitdiff;h=b3c6bdda38f7e370e1f80f02a61f1d3f08c1b57d\n>\n> here is the commit that fixed the problem for pacman. what do you think,\n> should we rename gitlink to something else, too - or should we contact\n> upstream to notify them about they caused a breakage?\n\nI've tried twice now to send a patch to the list...please let me know\nif it isn't working, because I am getting CCed on the send, and the\nmailing list address is set in the sendemail.to variable. I did notice\nthat send-email doesn't even prompt you for confirmation of the\ndefault \"to\" address if you have this variable set, so I'm not sure if\nsomething weird is happening there.\n\n-Dan\n"},{"id":"64180","messageId":"47767710.7040405@gmail.com","threadId":"11417","inReplyTo":"449c10960712290824yd2c5783l8d0ba91bbad95789@mail.gmail.com","subject":"[PATCH] Documentation: rename gitlink macro to linkgit","fromName":"Dan McGee","fromEmail":"dpmcgee@gmail.com","sentAt":"2007-12-29T16:34:24Z","receivedAt":"2007-12-29T16:34:24Z","isPatch":true,"sender":{"key":"dpmcgee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/265817?v=4"},"body":"On 12/29/2007 10:24 AM, Dan McGee wrote:\n> On Dec 29, 2007 9:57 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:\n>> http://code.toofishes.net/gitweb.cgi?p=pacman.git;a=commitdiff;h=b3c6bdda38f7e370e1f80f02a61f1d3f08c1b57d\n>>\n>> here is the commit that fixed the problem for pacman. what do you think,\n>> should we rename gitlink to something else, too - or should we contact\n>> upstream to notify them about they caused a breakage?\n> \n> I've tried twice now to send a patch to the list...please let me know\n> if it isn't working, because I am getting CCed on the send, and the\n> mailing list address is set in the sendemail.to variable. I did notice\n> that send-email doesn't even prompt you for confirmation of the\n> default \"to\" address if you have this variable set, so I'm not sure if\n> something weird is happening there.\n> \n> -Dan\n\n>From 68bf426e810e732ff3f9f75ffcd69f777b538685 Mon Sep 17 00:00:00 2001\nFrom: Dan McGee <dpmcgee@gmail.com>\nDate: Sat, 29 Dec 2007 00:20:38 -0600\nSubject: [PATCH] Documentation: rename gitlink macro to linkgit\n\nBetween AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock\nAsciidoc configuration:\n\n@@ -149,7 +153,10 @@\n # Inline macros.\n # Backslash prefix required for escape processing.\n # (?s) re flag for line spanning.\n-(?su)[\\\\]?(?P<name>\\w(\\w|-)*?):(?P<target>\\S*?)(\\[(?P<attrlist>.*?)\\])=\n+\n+# Explicit so they can be nested.\n+(?su)[\\\\]?(?P<name>(http|https|ftp|file|mailto|callto|image|link)):(?P<target>\\S*?)(\\[(?P<attrlist>.*?)\\])=\n+\n # Anchor: [[[id]]]. Bibliographic anchor.\n (?su)[\\\\]?\\[\\[\\[(?P<attrlist>[\\w][\\w-]*?)\\]\\]\\]=anchor3\n # Anchor: [[id,xreflabel]]\n\nThis default regex now matches explicit values, and unfortunately in this\ncase gitlink was being matched by just 'link', causing the wrong inline\nmacro template to be applied. By renaming the macro, we can avoid being\nmatched by the wrong regex.\n\nSigned-off-by: Dan McGee <dpmcgee@gmail.com>\n---\n Documentation/asciidoc.conf              |    8 +-\n Documentation/blame-options.txt          |    2 +-\n Documentation/cmd-list.perl              |    2 +-\n Documentation/config.txt                 |  126 +++++++++++++++---------------\n Documentation/cvs-migration.txt          |   10 +-\n Documentation/diff-options.txt           |    4 +-\n Documentation/everyday.txt               |   48 ++++++------\n Documentation/fetch-options.txt          |    2 +-\n Documentation/git-add.txt                |   16 ++--\n Documentation/git-am.txt                 |   16 ++--\n Documentation/git-annotate.txt           |    4 +-\n Documentation/git-apply.txt              |   12 ++--\n Documentation/git-archimport.txt         |    2 +-\n Documentation/git-archive.txt            |    2 +-\n Documentation/git-bisect.txt             |    2 +-\n Documentation/git-blame.txt              |    8 +-\n Documentation/git-branch.txt             |   12 ++--\n Documentation/git-bundle.txt             |   10 +-\n Documentation/git-cat-file.txt           |    4 +-\n Documentation/git-check-attr.txt         |    4 +-\n Documentation/git-check-ref-format.txt   |    6 +-\n Documentation/git-checkout-index.txt     |    2 +-\n Documentation/git-checkout.txt           |    4 +-\n Documentation/git-cherry-pick.txt        |    4 +-\n Documentation/git-cherry.txt             |    2 +-\n Documentation/git-citool.txt             |    6 +-\n Documentation/git-clean.txt              |    4 +-\n Documentation/git-clone.txt              |    2 +-\n Documentation/git-commit-tree.txt        |    6 +-\n Documentation/git-commit.txt             |   30 ++++----\n Documentation/git-config.txt             |    2 +-\n Documentation/git-count-objects.txt      |    2 +-\n Documentation/git-cvsexportcommit.txt    |    2 +-\n Documentation/git-cvsimport.txt          |    4 +-\n Documentation/git-cvsserver.txt          |    4 +-\n Documentation/git-daemon.txt             |    2 +-\n Documentation/git-describe.txt           |    2 +-\n Documentation/git-diff-files.txt         |    2 +-\n Documentation/git-diff-index.txt         |    2 +-\n Documentation/git-diff-tree.txt          |    2 +-\n Documentation/git-diff.txt               |    8 +-\n Documentation/git-fast-export.txt        |   12 ++--\n Documentation/git-fast-import.txt        |   18 ++--\n Documentation/git-fetch-pack.txt         |    4 +-\n Documentation/git-fetch.txt              |    4 +-\n Documentation/git-filter-branch.txt      |   16 ++--\n Documentation/git-fmt-merge-msg.txt      |    4 +-\n Documentation/git-format-patch.txt       |    8 +-\n Documentation/git-fsck-objects.txt       |    2 +-\n Documentation/git-fsck.txt               |    2 +-\n Documentation/git-gc.txt                 |   14 ++--\n Documentation/git-get-tar-commit-id.txt  |    4 +-\n Documentation/git-grep.txt               |    2 +-\n Documentation/git-gui.txt                |    4 +-\n Documentation/git-hash-object.txt        |    2 +-\n Documentation/git-help.txt               |    6 +-\n Documentation/git-http-fetch.txt         |    2 +-\n Documentation/git-http-push.txt          |    2 +-\n Documentation/git-imap-send.txt          |    2 +-\n Documentation/git-index-pack.txt         |   10 +-\n Documentation/git-init-db.txt            |    2 +-\n Documentation/git-init.txt               |    2 +-\n Documentation/git-instaweb.txt           |    2 +-\n Documentation/git-log.txt                |   10 +-\n Documentation/git-lost-found.txt         |    4 +-\n Documentation/git-ls-files.txt           |    8 +-\n Documentation/git-ls-remote.txt          |    4 +-\n Documentation/git-ls-tree.txt            |    2 +-\n Documentation/git-mailinfo.txt           |    4 +-\n Documentation/git-mailsplit.txt          |    2 +-\n Documentation/git-merge-base.txt         |    2 +-\n Documentation/git-merge-file.txt         |    4 +-\n Documentation/git-merge-index.txt        |    2 +-\n Documentation/git-merge-one-file.txt     |    2 +-\n Documentation/git-merge-tree.txt         |    2 +-\n Documentation/git-merge.txt              |    8 +-\n Documentation/git-mergetool.txt          |    4 +-\n Documentation/git-mktag.txt              |    2 +-\n Documentation/git-mktree.txt             |    2 +-\n Documentation/git-mv.txt                 |    2 +-\n Documentation/git-name-rev.txt           |    4 +-\n Documentation/git-pack-objects.txt       |   10 +-\n Documentation/git-pack-redundant.txt     |    8 +-\n Documentation/git-pack-refs.txt          |    2 +-\n Documentation/git-parse-remote.txt       |    2 +-\n Documentation/git-patch-id.txt           |    2 +-\n Documentation/git-peek-remote.txt        |    2 +-\n Documentation/git-prune-packed.txt       |    6 +-\n Documentation/git-prune.txt              |    2 +-\n Documentation/git-pull.txt               |   10 +-\n Documentation/git-push.txt               |    4 +-\n Documentation/git-quiltimport.txt        |    2 +-\n Documentation/git-read-tree.txt          |    8 +-\n Documentation/git-rebase.txt             |   10 +-\n Documentation/git-receive-pack.txt       |    4 +-\n Documentation/git-reflog.txt             |    8 +-\n Documentation/git-relink.txt             |    2 +-\n Documentation/git-remote.txt             |   12 ++--\n Documentation/git-repack.txt             |   14 ++--\n Documentation/git-repo-config.txt        |    2 +-\n Documentation/git-request-pull.txt       |    2 +-\n Documentation/git-rerere.txt             |    4 +-\n Documentation/git-reset.txt              |    8 +-\n Documentation/git-rev-list.txt           |   20 +++---\n Documentation/git-rev-parse.txt          |    2 +-\n Documentation/git-revert.txt             |    4 +-\n Documentation/git-rm.txt                 |    4 +-\n Documentation/git-send-email.txt         |    2 +-\n Documentation/git-send-pack.txt          |    6 +-\n Documentation/git-sh-setup.txt           |    2 +-\n Documentation/git-shell.txt              |    2 +-\n Documentation/git-shortlog.txt           |    2 +-\n Documentation/git-show-branch.txt        |    2 +-\n Documentation/git-show-index.txt         |    2 +-\n Documentation/git-show-ref.txt           |    6 +-\n Documentation/git-show.txt               |    8 +-\n Documentation/git-stash.txt              |   10 +-\n Documentation/git-status.txt             |    6 +-\n Documentation/git-stripspace.txt         |    2 +-\n Documentation/git-submodule.txt          |    6 +-\n Documentation/git-svn.txt                |   12 ++--\n Documentation/git-symbolic-ref.txt       |    2 +-\n Documentation/git-tag.txt                |    2 +-\n Documentation/git-tar-tree.txt           |    2 +-\n Documentation/git-unpack-file.txt        |    2 +-\n Documentation/git-unpack-objects.txt     |    2 +-\n Documentation/git-update-index.txt       |   12 ++--\n Documentation/git-update-ref.txt         |    2 +-\n Documentation/git-update-server-info.txt |    2 +-\n Documentation/git-upload-archive.txt     |    2 +-\n Documentation/git-upload-pack.txt        |    2 +-\n Documentation/git-var.txt                |    8 +-\n Documentation/git-verify-pack.txt        |    2 +-\n Documentation/git-verify-tag.txt         |    2 +-\n Documentation/git-whatchanged.txt        |    2 +-\n Documentation/git-write-tree.txt         |    2 +-\n Documentation/git.txt                    |   20 +++---\n Documentation/gitattributes.txt          |   10 +-\n Documentation/gitcli.txt                 |    2 +-\n Documentation/gitignore.txt              |    6 +-\n Documentation/gitk.txt                   |    6 +-\n Documentation/gitmodules.txt             |    6 +-\n Documentation/glossary.txt               |   18 ++--\n 143 files changed, 460 insertions(+), 460 deletions(-)\n\nLooks like the patch was bigger than I thought. Gzipped and attached if that is acceptable.\n"},{"id":"64393","messageId":"7vejcypqsp.fsf@gitster.siamese.dyndns.org","threadId":"11417","inReplyTo":"47767710.7040405@gmail.com","subject":"Re: [PATCH] Documentation: rename gitlink macro to linkgit","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-01-03T21:01:10Z","receivedAt":"2008-01-03T21:01:10Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Dan McGee <dpmcgee@gmail.com> writes:\n\n>>From 68bf426e810e732ff3f9f75ffcd69f777b538685 Mon Sep 17 00:00:00 2001\n> From: Dan McGee <dpmcgee@gmail.com>\n> Date: Sat, 29 Dec 2007 00:20:38 -0600\n> Subject: [PATCH] Documentation: rename gitlink macro to linkgit\n>\n> Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock\n> Asciidoc configuration:\n>\n> @@ -149,7 +153,10 @@\n>  # Inline macros.\n>  # Backslash prefix required for escape processing.\n>  # (?s) re flag for line spanning.\n> -(?su)[\\\\]?(?P<name>\\w(\\w|-)*?):(?P<target>\\S*?)(\\[(?P<attrlist>.*?)\\])=\n> +\n> +# Explicit so they can be nested.\n> +(?su)[\\\\]?(?P<name>(http|https|ftp|file|mailto|callto|image|link)):(?P<target>\\S*?)(\\[(?P<attrlist>.*?)\\])=\n> +\n>  # Anchor: [[[id]]]. Bibliographic anchor.\n>  (?su)[\\\\]?\\[\\[\\[(?P<attrlist>[\\w][\\w-]*?)\\]\\]\\]=anchor3\n>  # Anchor: [[id,xreflabel]]\n>\n> This default regex now matches explicit values, and unfortunately in this\n> case gitlink was being matched by just 'link', causing the wrong inline\n> macro template to be applied. By renaming the macro, we can avoid being\n> matched by the wrong regex.\n\nWhat's already tagged, released to the wild and picked up by\ndistros cannot be taken back, so I'd most likely have to apply\nyour patch anyway, but I have to say I am not very amused.  I'd\ncall this a regression on AsciiDoc's part.\n\nI would have expected some courtesy to make sure that updates to\nAsciiDoc would not to break existing users, especially the ones\nthat they use as the top advertising material in the \"Projects\nusing AsciiDoc\" list at http://www.methods.co.nz/asciidoc/ ;-)\n\nStuart, is there anything we can help you to set up some\nautomated tests to catch AsciiDoc regression, so we do not have\nto suffer like this again?\n"},{"id":"64409","messageId":"873ateyxjk.fsf@enceladus.ygingras.net","threadId":"11417","inReplyTo":"7vejcypqsp.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: rename gitlink macro to linkgit","fromName":"Yannick Gingras","fromEmail":"ygingras@ygingras.net","sentAt":"2008-01-04T05:22:55Z","receivedAt":"2008-01-04T05:22:55Z","isPatch":true,"sender":{"key":"ygingras@ygingras.net","avatar":"https://gravatar.com/avatar/9e1b648dd1e0ce5e42fb8be1ffbee13a0d5c9743b872ec312ae2dac4eee0c5bd?d=mp&s=160"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Stuart, is there anything we can help you to set up some automated\n> tests to catch AsciiDoc regression, so we do not have to suffer like\n> this again?\n\nWe considered adding a nose test suite.  The upcoming v9.0 release\ninvolves quite a bit of code massaging and we will definitely need an\nextensive test suite.  But the test suite can only catch obvious\nrendering failures so any help in eyeballing the output will be\nappreciated.\n\nShould we setup a distributed proof reading system like Project\nGutenberg?  I hope we don't need it.  But a few scripts to batch\nrender all the doc of popular projects would be nice.  We could upload\nsuch snapshot render jobs where everyone could take a quick glance and\nspot obvious rendering errors.\n\nIf you follow AsciiDoc's mailing list [1], we'll go through a series\nof release candidates before the final 9.0.  \"With enough eyeballs,\nall bugs are shallow.\"\n\n[1]: asciidoc-discuss@lists.metaperl.com\n\nI reply to two mailing lists; I think this particular problem belongs\nto asciidoc-discuss.\n\nBest regards, \n\n-- \nYannick Gingras\n"},{"id":"64410","messageId":"7vir2am95w.fsf@gitster.siamese.dyndns.org","threadId":"11417","inReplyTo":"873ateyxjk.fsf@enceladus.ygingras.net","subject":"Re: [PATCH] Documentation: rename gitlink macro to linkgit","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-01-04T05:50:19Z","receivedAt":"2008-01-04T05:50:19Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Yannick Gingras <ygingras@ygingras.net> writes:\n\n> Junio C Hamano <gitster@pobox.com> writes:\n>\n>> Stuart, is there anything we can help you to set up some automated\n>> tests to catch AsciiDoc regression, so we do not have to suffer like\n>> this again?\n>\n> We considered adding a nose test suite.  The upcoming v9.0 release\n> involves quite a bit of code massaging and we will definitely need an\n> extensive test suite.  But the test suite can only catch obvious\n> rendering failures so any help in eyeballing the output will be\n> appreciated.\n\nYou could go fancy like that, but I suspect that an automated\ntest to compare the text dump (e.g. \"links -dump doc.html\")\ngenerated by before and after version, perhaps with minimum\nmassaging, would go a long enough way.  At least that would have\ncaught the \"gitlink\" breakage, wouldn't it?\n"},{"id":"64411","messageId":"87fxxexgpu.fsf@enceladus.ygingras.net","threadId":"11417","inReplyTo":"7vir2am95w.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: rename gitlink macro to linkgit","fromName":"Yannick Gingras","fromEmail":"ygingras@ygingras.net","sentAt":"2008-01-04T06:11:41Z","receivedAt":"2008-01-04T06:11:41Z","isPatch":true,"sender":{"key":"ygingras@ygingras.net","avatar":"https://gravatar.com/avatar/9e1b648dd1e0ce5e42fb8be1ffbee13a0d5c9743b872ec312ae2dac4eee0c5bd?d=mp&s=160"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n>> But the test suite can only catch obvious rendering failures so any\n>> help in eyeballing the output will be appreciated.\n>\n> You could go fancy like that, but I suspect that an automated\n> test to compare the text dump (e.g. \"links -dump doc.html\")\n> generated by before and after version, perhaps with minimum\n> massaging, would go a long enough way.  At least that would have\n> caught the \"gitlink\" breakage, wouldn't it?\n\nYeah it would have caught it.  I'll hack something like that before\nthe 9.0 release.\n\n-- \nYannick Gingras\n"}]}