[Mesa-dev] abundance of branches in mesa.git

Emil Velikov emil.l.velikov at gmail.com
Sun Jun 21 09:22:12 PDT 2015

On 20/06/15 10:01, Eirik Byrkjeflot Anonsen wrote:
> Ilia Mirkin <imirkin at alum.mit.edu> writes:
>> Hello,
>> There are a *ton* of branches in the upstream mesa git. Here is a full list:
> [...]
>> is there
>> any reason to keep these around with the exception of:
>> master
>> $version (i.e. 9.0, 10.0, mesa_7_7_branch, etc)
> Instead of outright deleting old branches, it would be possible to set
> up an "archive" repository which mirrors all branches of the main
> repository. And then delete "obsolete" branches only from the main
> repository. Ideally, you would want a git hook to refuse to create a new
> branch (in the main repository) if a branch by that name already exists
> in the archive repository. Possibly with the exception that creating a
> same-named branch on the same commit would be allowed.
> (And the same for tags, of course)
Personally I am fine with either approach - stay/nuke/move. But I'm
thinking that having a mix of the two suggestions might be a nice middle

Write a script that nukes branches that are merged in master (check the
top commit of the branch) and have an 'archive' repo that contains
everything else (minus the stable branches).

On a mildly related topic - does anyone know what the 'mesa-test' repo
is all about ? There is a similar one for xorg-server, both of which
seems like a temporary experiment, which someone forgot to delete. There
hasn't been any response on #freedesktop on the topic.


More information about the mesa-dev mailing list