Re: GCC repo is locked?

> Am 25.07.2026 um 11:11 schrieb Jonathan Wakely via Gcc <[email protected]>:
>=20
> =EF=BB=BFOn Fri, 24 Jul 2026, 21:46 H.J. Lu via Gcc, <[email protected]> wro=
te:
>=20
>>> On Sat, Jul 25, 2026 at 4:29=E2=80=AFAM Mikael Morin <morin-mikael@orang=
e.fr>
>>> wrote:
>>>=20
>>> Le 24/07/2026 =C3=A0 22:00, H.J. Lu via Gcc a =C3=A9crit :
>>>> Hi,
>>>>=20
>>>> I have been trying to push for the last 15 minutes and getting:
>>>>=20
>>>> Enumerating objects: 18, done.
>>>> Counting objects: 100% (18/18), done.
>>>> Delta compression using up to 8 threads
>>>> Compressing objects: 100% (10/10), done.
>>>> Writing objects: 100% (10/10), 2.37 KiB | 485.00 KiB/s, done.
>>>> Total 10 (delta 8), reused 0 (delta 0), pack-reused 0 (from 0)
>>>> remote:
>> ---------------------------------------------------------------------
>>>> remote: --  Another user is currently pushing changes to this
>> repository.  --
>>>> remote: --  Please try again in another minute or two.
>>     --
>>>> remote:
>> ---------------------------------------------------------------------
>>>> remote: error: hook declined to update refs/heads/master
>>>>=20
>>>> Has anyone else seen this?
>>>>=20
>>> I'm afraid I'm (again) the cause of this.
>>> I posted a message on IRC telling anyone could kill the push hook
>>> process(es).  I'm not sure it reached the right people (or someone at
>> all).
>>=20
>> FWIW, I am using gitlab/github for my personal branches to avoid things
>> like this.
>>=20
>=20
>=20
> Yes, or forge.sourceware.org
>=20
> There's no good reason to use the main gcc.gnu.org repo for personal
> branches. And since this keeps happening maybe we should discourage or eve=
n
> disallow personal branches in the main repo. The server hooks that we want=

> in place for the official branches are not suitable for personal branches
> and just cause these problems.

Then just don=E2=80=99t run them =E2=80=A6. There must be also inefficiencie=
s in the scripts.

Richard=20=