From: Junio C Hamano <gitster@pobox.com>
To: Yannick Gingras <ygingras@ygingras.net>
Cc: asciidoc-discuss@lists.metaperl.com, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: rename gitlink macro to linkgit
Date: Thu, 03 Jan 2008 21:50:19 -0800 [thread overview]
Message-ID: <7vir2am95w.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <873ateyxjk.fsf@enceladus.ygingras.net> (Yannick Gingras's message of "Fri, 04 Jan 2008 00:22:55 -0500")
Yannick Gingras <ygingras@ygingras.net> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Stuart, is there anything we can help you to set up some automated
>> tests to catch AsciiDoc regression, so we do not have to suffer like
>> this again?
>
> We considered adding a nose test suite. The upcoming v9.0 release
> involves quite a bit of code massaging and we will definitely need an
> extensive test suite. But the test suite can only catch obvious
> rendering failures so any help in eyeballing the output will be
> appreciated.
You could go fancy like that, but I suspect that an automated
test to compare the text dump (e.g. "links -dump doc.html")
generated by before and after version, perhaps with minimum
massaging, would go a long enough way. At least that would have
caught the "gitlink" breakage, wouldn't it?
next prev parent reply other threads:[~2008-01-04 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 23:49 generated HTML contains broken links Eric Hanchrow
2007-12-29 3:01 ` Dan McGee
2007-12-29 15:57 ` Miklos Vajna
2007-12-29 16:24 ` Dan McGee
2007-12-29 16:34 ` [PATCH] Documentation: rename gitlink macro to linkgit Dan McGee
2008-01-03 21:01 ` Junio C Hamano
2008-01-04 5:22 ` Yannick Gingras
2008-01-04 5:50 ` Junio C Hamano [this message]
2008-01-04 6:11 ` Yannick Gingras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vir2am95w.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=asciidoc-discuss@lists.metaperl.com \
--cc=git@vger.kernel.org \
--cc=ygingras@ygingras.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.