----- Original Message -----
From: "Joseph Rushton Wakeling" <joseph.wakel...@webdrake.net>
To: "Phil Holmes" <m...@philholmes.net>
Cc: "James" <pkx1...@gmail.com>; <lilypond-devel@gnu.org>
Sent: Saturday, October 06, 2012 5:26 PM
Subject: Re: [talk] why it'd be great to have web interface for
submittingsimple doc patches
On 10/06/2012 05:46 PM, Phil Holmes wrote:
As you say, compile-edit-compile cycles are shorter than the full build,
but can
occasionally not reveal errors, so for a proper test it's always better
to nuke
the build directory and rebuild from scratch.
Out of curiosity, what kind of errors? I imagine stuff involving
cross-references, the index, etc.?
It's more that there are a variety of outputs generated from the doc
source - pdf, split html, large html, info, etc. - to be sure that the
source is OK you need to be certain all have been generated and therefore
checked, and the simplest way of ensuring that is from a clean build.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
