Issue 4425: Fix some CG musing about music functions

[lilypond.git] / Documentation / contributor / administration.itexi

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 787a0994631096bc8f891476fd93bd99467c843d..50f97ade9e6ef4370912c18025436f5a0ad87906 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -197,7 +197,7 @@ by default.
 @node Patchy requirements
 @subsection Patchy requirements
 
-@unnumberedsubsec Testing new patches
+@subsubsubheading Testing new patches
 
 @itemize
 
@@ -217,10 +217,18 @@ documentation.  See @ref{Compiling}.
 Commit access is @emph{not} required to test patches, but a valid login
 to @uref{http://code.google.com/} @emph{is}.
 
+@noindent
+Note that a google account does not need to be a Gmail account; you can
+use @emph{any} email address for your google account when you sign up.
+
+@warning{In order for @code{patchy} to work as expected, your Google
+Account Settings must have the @q{Access for less secure apps} set to
+@q{Allowed}.  This is normally the default setting.}
+
 @end itemize
 
 
-@unnumberedsubsec Testing & pushing new commits
+@subsubsubheading Testing & pushing new commits
 
 @itemize
 
@@ -359,7 +367,7 @@ instances of Patchy being run locally at the same time.
 @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
@@ -408,7 +416,7 @@ tests fail, do not try to push your own fixes but report the failures to
 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
@@ -537,7 +545,7 @@ Issue 4008: Testing patch issue115770043_1_diff
 
 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
@@ -561,7 +569,7 @@ sh ~/lilypond-auto-compile-results/show-regtests-4007
 
 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