Bob Proulx <[email protected]> writes: >> What are the recommended URLs to use in documentation? >> "https://{https,cgit,gitweb}.git.savannah.gnu.org"; or >> "https://git.savannah.gnu.org";? > > That is a good question. I know people prefer shorter ones (Look at > the shorter debbugs URLs for an example) and the redirects will then > go to the best place. But that does require the primary to be online > and available and fails if it is not. Whereas the longer URLs to the > mirror pool will work independently of the primary. > > With the redirects in place the load on the primary has been reduced > hugely. Basically reduced from 40+ with 100% of 8-cpus down to an > average of 2 with idle cpu available. And so perhaps I no longer feel > strongly about it one way or the other until and unless some new > problem arises. > > Do you have an opinion? What do you think?
Personally, I prefer to be on the safe side and use the long URLs. Now that they are stable I think they are perfectly fine for documentation. Also, https://cgit.git.savannah.gnu.org/cgit/REPO points to git://git.git.savannah.gnu.org/REPO and https://https.git.savannah.gnu.org/git/REPO. So, using the long URLs for everything seems more consistent. Does it make sense? > Yes your address might have been blocked by tripping one of the rules. > If you tell us your address (you can seen it privately to the private > [email protected] list) then we can look to see if so > and why. And we would need to know which system you were connecting > to as well. Since as described they are both independent and coupled > and we would need to look both places. No worries. I have access again and now that I know that I can be blaclisted I'll avoid doing "unusual" actions. In any case, given that the long URLs are stable, I'll use those. And, most of the time, I use SSH to work with the repos. Thanks a lot for your work and help! Roi
