git branches
Project / Subsystem
binutils / binutils
Date
2026-05-12
Proposer
Jan Beulich <jbeulich@suse.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Requires a policy decision and consistent enforcement.
- • May inconvenience developers who are accustomed to the current layout.
All attributes
- project
- binutils
- subsystem
- binutils
- patch_id
- —
- discussion_id
- 7737a224-755c-4c5b-bc7b-3de165f8a254@suse.com
- source_type
- public_inbox
- title
- git branches
- headline
- Request tidier binutils git branch organization.
- tldr
- Jan Beulich suggests tidying the binutils git repository by keeping only official branches at the top level and moving user branches under `users/`.
- proposer
- Jan Beulich <jbeulich@suse.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Requires a policy decision and consistent enforcement.
- • May inconvenience developers who are accustomed to the current layout.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • binutils
- • git
- • repository
- • branching
- • organization
- bugzilla_url
- —
- date
- 2026-05-12T00:00:00.000Z
git branches
Jan Beulich suggests organizing the binutils git repository by limiting the top-level branches to official ones, and placing user-specific branches under the users/ namespace. This is to reduce the amount of data fetched by developers who selectively fetch branches.