X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fcontributor%2Fquick-start.itexi;h=d41b7ad3e7d06169474acdb3893a61e358cca418;hb=337a44f3493f54e2fdd6ff3af06fe4fb84f549fe;hp=9a5b12a7ec36d597e6eef5875588c2d65ec6c4d5;hpb=306c0929457ca5dd92a8f5edeb72515301e55c87;p=lilypond.git

diff --git a/Documentation/contributor/quick-start.itexi b/Documentation/contributor/quick-start.itexi
index 9a5b12a7ec..d41b7ad3e7 100644
--- a/Documentation/contributor/quick-start.itexi
+++ b/Documentation/contributor/quick-start.itexi
@@ -362,7 +362,7 @@ After entering a commit message, click @qq{OK} to finalize the
 commit.
 
 @advanced{for more information regarding commits and commit
-messages, see @ref{Commits and patches}.}
+messages, see @ref{Commits}.}
 
 
 @subsubheading 2b. Amend previous commit
@@ -508,30 +508,40 @@ This will download and update you to the lastest version of git-cl.
 @node Configuring git-cl
 @unnumberedsubsec Configuring @code{git-cl}
 
-@subsubheading Set up login accounts
-
 Because @code{git-cl} updates two separate websites (Google's Rietveld
 Code Review Tool and LilyPond's issue tracker) you @emph{must} have a
 valid user account (login and password) for both sites.
 
+@subsubheading Set up a login account for Rietveld Code Review Tool
+
 @noindent
-For the Rietveld Code Review Tool you will need a Google account.  Note
-that a Google account does not require that you have or use a @q{Google}
-email address.  You can use @emph{any} email address for your Google
-account.  Just select the option @qq{I prefer to use my current email
-address} when you sign up.
+For the Rietveld Code Review Tool you will need a Google account but
+this does @emph{not} require @q{Google} email address; i.e. @emph{any}
+email address for your Google account can be used.  Just select the
+option @qq{I prefer to use my current email address} when you sign up
+with Google.
+
+@warning{In order for @code{git-cl} to work correctly with this Google
+account, your Google Account Settings must have the
+@q{Access for less secure apps} set to @q{Allowed} -- this is normally
+the default setting.}
+
+@subsubheading Set up a login account for LilyPond's Issue Tracker
 
-@warning{In order for @code{git-cl} to work, your Google Account
-Settings must have the @q{Access for less secure apps} set to
-@q{Allowed}.  This is normally the default setting.}
+@noindent
+Please register a user account at
+@code{https://sourceforge.net/user/registration} preferably using the
+same email address that you want to use LilyPond Developer mailing list
+login.
 
 @noindent
-For the LilyPond issue tracker, please request a user account by sending
-an email to the LilyPond Developer's mailing list
-(@code{lilypond-devel@@gnu.org}), preferably using the same email
-address that you want to use for your user login.
+Once you have created this Sourceforge user account, send an email to
+the LilyPond Developer's mailing list (@code{lilypond-devel@@gnu.org})
+asking for write access to the issue tracker along with your Sourceforce
+@emph{Username} (not email address) and someone will then be able to set
+this up for you.
 
-@subsubheading Authorising git-cl for the LilyPond issue tracker
+@subsubheading Authorizing git-cl for the LilyPond issue tracker
 
 The @code{git-cl} command itself also needs to be @q{authorized} so that
 it can access the LilyPond issue tracker.
@@ -558,6 +568,27 @@ tracker.
 
 @end enumerate
 
+@subsubheading Installing ca-certificates
+
+In order to have @code{git-cl} properly update issues on the SourceForge
+Allura issue tracker, you must have the package @code{ca-certificates}
+installed.  You can check to see if the package is installed with
+
+@example
+apt --installed list | grep ca-certificates
+@end example
+
+If @code{ca-certificates} is installed, you will get a result that shows
+the version that is installed.  If it is not installed, there will be
+no version displayed.
+
+Install @code{ca-certificates} with the following:
+
+@example
+sudo apt-get install ca-certificates
+@end example
+
+
 @subsubheading Running git-cl for the first time
 
 @enumerate