> Date: Thu, 22 May 2025 16:51:38 -0600 > From: Karl Berry <[email protected]> > Cc: [email protected] > > Thus I suggest changing the emacs public info to give people with sv > accounts the alternative of getting access over git://. Along the lines of: > > If you have a Savannah account (need not be a member of the emacs group): > git clone [email protected]:/srv/git/emacs.git
Doesn't this require SSH setup for use with Git on the system from which this is done? > If you don't have an account (much less reliable): > git clone https://git.savannah.gnu.org/git/emacs.git FWIW, I don't hear any complaints about the reliability of HTTPS non-member access, although there are quite a few people who track the Emacs development branches without having write access to the repository. So I'm not sure how serious this problem is. > (You can register for an account at > https://savannah.gnu.org/account/register.php.) Do we really want gobs of people asking for a Savannah account as result of the above?
