On Fri, May 23, 2025 at 08:38:48AM +0300, Eli Zaretskii wrote: > > 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?
Yes; the user has to register an SSH key and use it with Git. > > 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. Probably it is; if it weren't, the admins wouldn't be setting up a net of mirrors. > > (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? Making an account requires no action from anybody but the user who makes the account---spammers make 10 to 30 accounts daily, and they are removed either immediately or two weeks later due to inactivity. in order to make an account persistent, it's sufficient to comment from it on any tracker, like "I'll use this account for Git access"---and the account automatically becomes "non-idle". So this isn't an issue; what may be more important is that people may be unwilling to create any accounts at all (or use SSH).
signature.asc
Description: PGP signature
