Re: Cleaning up branches on savannah

[Mark H Weaver <mhw@netris.org>]

Christopher Baines <mail@cbaines.net> writes:

> There are quite a few branches on savannah, and it would be nice to
> remove them if they're unnecessary, at least because that will prompt
> the QA data service to delete the data, saving on disk space.
[...]
> The following branches all seem to have commits that haven't made it to
> master yet, although I haven't checked if the changes were applied but
> just with different commit ids.
>
>  - gnuzilla-updates

The changes to 'gnuzilla-updates' were applied to 'master' but with
different commit ids.

In general, whenever there's an update to IceCat, which typically
happens about once per month, I delete the 'gnuzilla-updates' branch and
then immediately push a new one that is current 'master' plus the
untested commit(s) for the IceCat update.  This triggers the
'gnuzilla-updates' jobset on ci.guix.gnu.org to build the new IceCat.
Later, when I'm satisfied that the new IceCat works, I push the update
to 'master' as separate commits.  Usually, the new commit(s) on 'master'
are precisely the same as the ones on the 'gnuzilla-updates' branch
except for the commit log message.

If there's a better way to do this that does not entail much more work
for me, please let me know.

      Thanks,
        Mark