Re: GCC repo is locked?

Project / Subsystem

gcc / gcc

Date

2026-07-25

Proposer

Jonathan Wakely <jwakely.gcc@gmail.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

/10

Technical tradeoffs

  • Potential inconvenience for developers who prefer using the main repository for all their work.
  • Requires developers to manage separate repositories for personal work, adding a small layer of complexity.
  • Improved stability and reliability of the main repository's push operations.

All attributes

project
gcc
subsystem
gcc
patch_id
discussion_id
CAH6eHdQOFhEcT5knmeUOgb2Y3edmJxTpE16TwO8k=GSwB2MVfA@mail.gmail.com
source_type
public_inbox
title
Re: GCC repo is locked?
headline
Discourage personal branches in the main GCC repository
tldr
Discussion on discouraging or disallowing personal branches in the main GCC repository due to recurring push hook issues.
proposer
Jonathan Wakely <jwakely.gcc@gmail.com>
consensus
Proposed
outcome
proposed
sentiment_score
technical_tradeoffs
  • Potential inconvenience for developers who prefer using the main repository for all their work.
  • Requires developers to manage separate repositories for personal work, adding a small layer of complexity.
  • Improved stability and reliability of the main repository's push operations.
series_id
series_role
standalone
series_parts
[]
tags
  • repository management
  • git
  • workflow
  • infrastructure
bugzilla_url
date
2026-07-25T00:00:00.000Z

Re: GCC repo is locked?

This thread discusses recent issues with the GCC repository being temporarily locked due to users pushing personal branches, which interferes with server hooks intended for official branches. Jonathan Wakely suggests that personal branches should be discouraged or disallowed in the main repository, recommending alternatives like personal gitlab/github repositories or forge.sourceware.org for such work to avoid recurring problems with server hooks.