> 2) I also notice that some packages, notably
> https://savannah.gnu.org/projects/emacs
> advertises
> git clone https://git.savannah.gnu.org/git/emacs.git
> as the way to get the repo in their "public info".
> Eli, maybe that's something you'd like to change?
If someone tells me what this should be changed to and why, I could
consider doing that, yes. ATM I admit I don't understand what is
wrong with that info: does it not work or something?
git operations over https, among other things, frequently fail nowadays
because of the endless AI crawling overloading the server, as I'm sure
you're well aware. That's what the bombardment of reports about git
clone https://... failing over the last few months have been
about. Many, perhaps most, of the reports have been for emacs, from what
I've seen.
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
If you don't have an account (much less reliable):
git clone https://git.savannah.gnu.org/git/emacs.git
(You can register for an account at
https://savannah.gnu.org/account/register.php.)
Karl
