Hi Ineiev,
I changed "Member clone" to "Authenticated SSH access", with a note
telling when it's read-write and when it's read-only. Please check
if anything is wrong.
Checking https://savannah.gnu.org/git/?group=emacs
it looks good to me. I have no additional comments about that.
But now, looking at the UsingGit wiki page that is linked there, I think
the same sort of update would be useful in that list of urls at the
top. Right now the ssh://git.savannah.gnu.org/srv/git/mygroup.git is
said to be only for read/write member access.
Also, I believe the http:// urls of the last two now automatically
redirect to https, so might as well write them with https in the first
place, if they're still relevant. (They did work.)
Also, instead of bolding two items in the middle of the list, I think it
would rather more parsable to write the recommended ones first, in one
list (including the new svuser read-only access), and then the other
ones in a second list. With some explanation as to the current woes of
https://git.savannah.gnu.org.
But finally, now I'm confused again. The first url in the list is
git://git.savannah.gnu.org/mygroup.git
and indeed, for example,
git clone git://git.savannah.gnu.org/config.git
apparently works fine.
So wouldn't this be the simplest/best way to get an anonymous read-only
checkout for anyone, not requiring an sv account and not using https?
Is there an advantage to the ssh/member method for readonly? -k
