Doc: CG: more tips for Issues.

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 72509d080f72c0172afe2166e7cce1b150f6c3b4..5748f78cc8ba159f089c09aae2eab4e562fc32ae 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -58,16 +58,19 @@ from @ref{Bug Squad checklists}.
 If you do not have one already, create a gmail account and send
 the email address to the @ref{Meisters, Bug Meister}.
 
+@item
+Subscribe your gmail account to @code{bug-lilypond}.
+
 @item
 Configure your google code account:
 
 @enumerate
 
 @item
-Log in to:
+Sign in to google code by clicking in the top-right corner of:
 
 @example
-@uref{http://code.google.com}
+@uref{http://code.google.com/p/lilypond/issues/list}
 @end example
 
 @item
@@ -315,6 +318,11 @@ version; if you cannot reproduce the bug, mark the item
 @uref{http://code.google.com/p/lilypond/issues/list?can=7}
 @end example
 
+A few (approximately 10%) of these fixed issues relate to the
+build system or fundamental architecture changes; there is no way
+for you to verify these.  Leave those issues alone; somebody else
+will handle them.
+
 @end itemize