On Sun, 16 Mar 2025, 22:16 Mark Wielaard, <m...@klomp.org> wrote: > Hi Harald, > > On Sun, Mar 16, 2025 at 10:57:08PM +0100, Harald Anlauf wrote: > > I have never tried any complex setups besides simple ssh tunnels > > with git in the past, so believe this does not apply. > > > > Doing even a simple ssh -Tvv to gcc.gnu.org takes a very long time > > when trying in parallel to the git command. And empirically this > > seems to happen only during a certain time of the day. > > That is really odd. If you are using ssh then there shouldn't be any > throtteling and you shouldn't really be affected by current http based > ddos. It might be your local network? > > I just did a clean clone of the whole gcc.git which took ~8 minutes > over http and ~5 minutes over ssh. So cloning/pulling over https is > certainly slower, but you should get reasonable speeds over https. > > > Regarding your comment on using github for fetching (and keeping > > gcc.gnu.org for push), the gcc website does not give a recommendation > > on how to use that in practice. Could we update > > https://gcc.gnu.org/about.html#git > > and/or > > https://gcc.gnu.org/gitwrite.html > > with best practices? > > I don't think anybody wants to recommend github for these things. >
Right, it's not "best practice", I was suggesting it as an alternative because fetching from gcc.gnu.org is taking *hours* for you. That isn't happening for anybody else, so it doesn't seem worth putting in the docs. https://giveupgithub.com Also those aren't under our control. If you > really need a mirror then try the ones at https://forge.sourceware.org/ > or https://git.sr.ht/~sourceware/ which we keep up to date. > > Cheers, > > Mark >
