Alfred M. Szmidt wrote: > > Bob Proulx wrote: > If it is not documented then using it is using an undocumented > interface. Undocumented interfaces are not guarenteed to continue to > exist. And I remember this one because it didn't exist for at least a > couple of years! But then we got some reports that people complained > that it should work. Not knowing where to point it to we pointed it > to git.savannah.gnu.org because that was back when I was new and not > as assertive about removing undocumented features. > > I'm not sure what documentation you keep refering to, but git.gnu.org > et al have existed and worked for the past ~15 years (probobly > longer), when I think I asked for them to be added back then.
That is simply not true. Years have gone by and there are too many mailing lists and I do not find mailing list discussion. But I do have my commit logs to the test suite. commit 153eadef831c242a3daa380a71b3b63f452ea2a1 Author: Bob Proulx <[email protected]> Date: Sun Jul 22 16:55:30 2018 -0600 Add git.gnu.org which is apparently a thing. Although git.gnu.org has never been advertised it is apparently a thing and is used by at least one user. Check for it. However just the basic git and ssh protocols since there is no https certificate as there has never been an https certificate and I don't want to expand to either https or http. That might be changed due to demand though. Definitely at that time there was no https certificates for git.gnu.org and no http support either. I double checked the nginx configuration and there was no support for http for git.gnu.org at that time either. Only ssh:// and git:// support was functional at that time. Support for http was not added until 2023. commit 54145228ec2c6e875236f870c17a646b4807441a Author: Bob Proulx <[email protected]> Date: Fri Jan 27 13:15:05 2023 -0700 Add support for https://git.gnu.org Due to request by jemarch I have added https and http support for using the alias name git.gnu.org to Savannah. This added configuation to the Nginx web server and the associated https certificates. This test expansion expands on the 2018 addition which added git://git.gnu.org to the tests. Saying that the git.gnu.org alias has always been there and always worked is simply not a true statement. > git.gnu.org always pointed to git.sv.gnu.org. > > There is nothing "undocumented" about it. Where is it documented? If one goes to the Savannah page for Coreutils then one sees these documented. https://savannah.gnu.org/git/?group=coreutils git clone https://git.savannah.gnu.org/git/coreutils.git git clone [email protected]:/srv/git/coreutils.git If one goes to the cgit page, and it does not time out due to the current abuse problem, then one sees these advertised. https://git.savannah.gnu.org/cgit/coreutils.git/ git://git.savannah.gnu.org/coreutils.git https://git.savannah.gnu.org/git/coreutils.git ssh://git.savannah.gnu.org/srv/git/coreutils.git If one looks at the wiki pages then one sees these: https://savannah.gnu.org/maintenance/UsingGit/ git clone https://git.savannah.gnu.org/git/group.git git clone git://git.savannah.gnu.org/group.git git clone ssh://[email protected]/srv/git/group.git git clone [email protected]:/srv/git/group.git ssh://[email protected]/srv/git/group.git All of those are examples documenting the interfaces. A large effort is made not to break documented interfaces. If people use undocumented interfaces then those interfaces might change. Bob
