@node Patchy requirements
@subsection Patchy requirements
-@unnumberedsubsec Testing new patches
+@subsubsubheading Testing new patches
@itemize
@end itemize
-@unnumberedsubsec Testing & pushing new commits
+@subsubsubheading Testing & pushing new commits
@itemize
@node Running the scripts
@subsection Running the scripts
-@unnumberedsubsec Testing & pushing new commits
+@subsubsubheading Testing & pushing new commits
@code{lilypond-patchy-staging.py} is run @emph{without} any arguments.
It then checks to see if @code{remote/origin/staging} is
the Developers List <lilypond-devel@@gnu.org> for advice.}
-@unnumberedsubsec Testing new patches
+@subsubsubheading Testing new patches
When run without any argument, @code{test-patches.py} will check
@uref{http://code.google.com/p/lilypond/issues/list} for all tracker
and so on.
-@unnumberedsubsubsec Checking the regression test results
+@subsubsubheading Checking the regression test results
Assuming the patch passed all the @code{make} tests, the regression
differences will be located in the @file{/test-results/} directory
See @ref{Regression tests}.
-@unnumberedsubsec Reporting test results
+@subsubsubheading Reporting test results
Once a patch has been tested and the regression tests have been
manually checked, the tracker can be updated manually by editing the
@seealso
Referencia de funcionamiento interno:
-@rinternals{Engraver_group},
@rinternals{Note_heads_engraver},
@rinternals{Text_engraver},
@rinternals{Rhythmic_column_engraver},