From: Valentin Villenave <v.villenave@gmail.com>
Date: Thu, 27 May 2010 17:14:00 +0000 (+0200)
Subject: Doc: add subheadings to CG "Regtests"
X-Git-Tag: release/2.13.23-1~29^2~17
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=6be6c335f7e61cb258351fd5850f4aab9da8be42;p=lilypond.git

Doc: add subheadings to CG "Regtests"
---

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index e8df94609d..a6106cea93 100644
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -38,6 +38,15 @@ of different versions to see when bugs appeared.
 
 @TODO: To be checked and completed -vv
 
+Regression tests (@qq{regtests}) are available in two ways: either
+in a compiled form, for instance on the website, or as source code
+that needs to be compiled locally, using the most recent LilyPond
+binary as possible.  The latter is recommended, although more
+technically involved.
+
+
+@subheading Precompiled regtests
+
 The easiest way to see the @q{current} regtest output (meaning,
 the ouput of the latest stable or development version) is
 to look at the precompiled regtest
@@ -51,6 +60,9 @@ features, bugfixes... or new bugs that may have been introduced!
 Therefore, if you have an appropriate environment to build LilyPond
 yourself, it is recommended that you compile the software yourself.
 
+
+@subheading Compiling regtests
+
 The first step is to download the latest available source code,
 as explained in @ref{Working with source code}.  Then you will need
 to build the LilyPond binary@footnote{Uninstalling the previous