Problems accessing source code?

[chris hermansen]

Thank you for your kind and informative reply, Mark.

On Mon, Aug 24, 2026 at 1:24 AM Mark Wielaard <mark@klomp.org> wrote:
>
> Hi Chris,
>
> On Sun, Aug 23, 2026 at 09:03:41PM -0700, chris hermansen wrote:
> > Good evening all,
> >
> > Anyone besides me having difficulties with:
> >
> > git clone https://gcc.gnu.org/git/gcc.git
> >
> > I've been getting
> >
> > error: RPC failed; HTTP 429 curl 22 The requested URL returned error: 429
> >
> > and sometimes
> >
> > fatal: the remote end hung up unexpectedly
> >
> > over the course of the day (Pacific time)
>
> Sadly yes. The AI scraperbots are again in full force using
> residential proxies. An nginx limiter was put in front the
> sourceware/gcc/cygwin https to fight them off. But innocent bystanders
> get hit by the mitigation too. One way to get around the limiter is
> login in to bugzilla or use ssh (assuming you have an account on the
> system).
>
> The other is to use a non-https protocol like git:// or use the forge
> mirror git clone https://forge.sourceware.org/gcc/gcc or sourcehut one
> git clone https://git.sr.ht/~sourceware/gcc

I have cloned the repository from the forge.sourceware.org site; thank
you very much for that pointer.
-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.