doc: Update section on "commit access"

Documentation/contributor/source-code.itexi

 @c -*- coding: utf-8; mode: texinfo; -*-
 
 
 @node Working with source code
 @chapter Working with source code
 
 @warning{New contributors should read @ref{Quick start}, and in
 particular @ref{lily-git}, instead of this chapter.}
 
 Advanced contributors will find this material quite useful,
@@ skipping 1986 matching lines @@
 (@email{lilypond-devel@@gnu.org}).  Generally, only contributors
 who have already provided a number of patches which have been
 pushed to the main repository will be considered for membership.
 
 If you have been approved by the Project Manager, use the
 following procedure to obtain commit access:
 
 @enumerate
 @item
 If you don't already have one, set up a Savannah user account at
-@uref{https://savannah.gnu.org/account/register.php}.  If your web
-browser responds with an @qq{untrusted connection} message when
-you visit the link, follow the steps for including the CAcert root
-certificate in your browser, given at
-@uref{http://savannah.gnu.org/tls/tutorial/}.
+@uref{https://savannah.gnu.org/account/register.php}.
 
 @warning{Savannah will silently put your username in lower-case --
 do not try to use capital letters.}
 
 
 @item
 After registering, if you are not logged in automatically, login
 at @uref{https://savannah.gnu.org/account/login.php}---this should
 take you to your @qq{my} page
 (@uref{https://savannah.gnu.org/my/}).
@@ skipping 19 matching lines @@
 
 @example
 ssh-keygen -t rsa
 @end example
 
 When prompted for a location to save the key, press <ENTER> to
 accept the default location (@file{~/.ssh/id_rsa}).
 
 Next you are asked to enter an optional passphrase.  On most
 systems, if you use a passphrase, you will likely be prompted for
-it every time you use @command{git@tie{}push} or
-@command{git@tie{}pull}.  You may prefer this since it can protect
+it every time you use @command{git push} or
+@command{git pull}.  You may prefer this since it can protect
 you from your own mistakes (like pushing when you mean to pull),
 though you may find it tedious to keep re-entering it.
 
 You can change/enable/disable your passphrase at any time with:
 
 @example
 ssh-keygen -f ~/.ssh/id_rsa -p
 @end example
 
 Note that the GNOME desktop has a feature which stores your
@@ skipping 24 matching lines @@
 @example
 Success: Key #1 seen Keys registered
 @end example
 
 
 @item
 Configure Git to use the SSH protocol (instead of the GIT
 protocol).  From your local Git repository, enter:
 
 @example
-git config remote.origin.url \
-  ssh://@var{user}@@git.sv.gnu.org/srv/git/lilypond.git
+git remote set-url origin ssh://@var{user}@@git.sv.gnu.org/srv/git/lilypond.git
 @end example
 
 @noindent
 replacing @var{user} with your Savannah username.
 
 
 @item
 After your membership has been activated and you've configured Git
 to use SSH, test the connection with:
 
@@ skipping 20 matching lines @@
 Warning: Permanently added 'git.sv.gnu.org,140.186.70.72' (RSA) to
 the list of known hosts.
 @end example
 
 The list of known hosts is stored in the file
 @file{~/.ssh/known_hosts}.
 
 At this point, you are prompted for your passphrase if you have
 one, then Git will attempt a pull.
 
-If @command{git@tie{}pull@tie{}--verbose} fails, you should see
+If @command{git pull --verbose} fails, you should see
 error messages like these:
 
 @example
 Permission denied (publickey).
 fatal: The remote end hung up unexpectedly
 @end example
 
 If you get the above error, you may have made a mistake when
 registering your SSH key at Savannah.  If the key is properly
 registered, you probably just need to wait for the Savannah server
 to activate it.  It usually takes a few minutes for the key to be
 active after registering it, but if it still doesn't work after an
 hour, ask for help on the mailing list.
 
-If @command{git@tie{}pull@tie{}--verbose} succeeds, the output
+If @command{git pull --verbose} succeeds, the output
 will include a @q{From} line that shows @q{ssh} as the protocol:
 
 @example
 From ssh://git.sv.gnu.org/srv/git/lilypond
 @end example
 
 If the protocol shown is not @q{ssh}, check that you configured
 Git properly in the previous step.
 
 
@@ skipping 26 matching lines @@
 making commits, or you may simply copy the files from your
 local @file{~/.ssh} folder to the same folder on the other
 machine.
 
 @end enumerate
 
 @subsubheading Technical details
 
 @itemize
 @item
-On Firefox, to view or remove the CAcert root certificate, go to:
-Edit > Preferences > Advanced > Encryption > View Certificates >
-Authorities > Certificate Name > Root CA > CA Cert Signing
-Authority.
-
-@item
-The @command{git@tie{}config} commands above should modify your
+The @command{git remote @w{set-url}} command above should modify your
 local repository's @file{.git/config} file.  These lines:
 
 @example
 [remote "origin"]
         url = git://git.sv.gnu.org/lilypond.git/
 @end example
 
 @noindent
 should now be changed to:
 
 @example
 [remote "origin"]
         url = ssh://@var{user}@@git.sv.gnu.org/srv/git/lilypond.git
 @end example
 
 @noindent
 where @var{user} is your login name on Savannah.
 
 @item
 Similarly, the
-@command{git@tie{}config@tie{}push.default@tie{}matching} command
+@command{git config @w{push.default} matching} command

[lemzwerg, 2019/10/25 17:02:22]

This @w{} command is not necessary, since a full stop is not a hyphen-like
character.

 should add these lines to @file{.git/config}:
 
 @example
 [push]
         default = matching
 @end example
 @end itemize
 
 @knownissues
 Encryption protocols, including ssh, generally do not permit packet
@@ skipping 490 matching lines @@
 
 @item
 Book about git: @uref{http://progit.org/,Pro Git}
 
 @item
 Github help: @uref{http://help.github.com/}
 (very highly recommended by Graham)
 
 @end itemize