Re: GCC repo is locked?
Project / Subsystem
gcc / gcc
Date
2026-07-25
Proposer
Richard Biener <richard.guenther@gmail.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Centralizing personal branches in the main repository simplifies some workflows but increases the risk of such lockouts.
- • Using external hosting for personal branches reduces contention on the main repository but adds an extra step for developers.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- 89A5A301-A04D-4C36-8226-6CDFCF5BD8B1@gmail.com
- source_type
- public_inbox
- title
- Re: GCC repo is locked?
- headline
- GCC repo is locked?
- tldr
- Repository push hook issues prompt discussion on using main repo for personal branches.
- proposer
- Richard Biener <richard.guenther@gmail.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Centralizing personal branches in the main repository simplifies some workflows but increases the risk of such lockouts.
- • Using external hosting for personal branches reduces contention on the main repository but adds an extra step for developers.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • git
- • repository
- • access
- • hooks
- bugzilla_url
- —
- date
- 2026-07-25T00:00:00.000Z
Re: GCC repo is locked?
A user reported being unable to push to the GCC repository due to a “Another user is currently pushing” message, indicating a lock on the repository. This has recurred, leading to a discussion about discouraging or disallowing personal branches in the main repository, with suggestions to use external hosting like Gitlab or sourceware.org instead.