GCC repo is locked?

[Jonathan Wakely]

On Fri, 24 Jul 2026, 21:46 H.J. Lu via Gcc, <gcc@gcc.gnu.org> wrote:

> On Sat, Jul 25, 2026 at 4:29 AM Mikael Morin <morin-mikael@orange.fr>
> wrote:
> >
> > Le 24/07/2026 à 22:00, H.J. Lu via Gcc a écrit :
> > > Hi,
> > >
> > > I have been trying to push for the last 15 minutes and getting:
> > >
> > > 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
> > >
> > > Has anyone else seen this?
> > >
> > 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).
>
> FWIW, I am using gitlab/github for my personal branches to avoid things
> like this.
>


Yes, or forge.sourceware.org

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 even
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.