From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Re: Cleaning up branches on savannah
Date: Wed, 19 Jun 2024 15:03:57 +0100 [thread overview]
Message-ID: <87h6dp3u7m.fsf@cbaines.net> (raw)
In-Reply-To: <871q592ixj.fsf@cbaines.net> (Christopher Baines's message of "Fri, 07 Jun 2024 10:36:40 +0100")
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> 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
> - go-team
> - haskell-team
> - hurd-team
> - install-doc-overhaul
> - kernel-updates
> - node-18-updates
> - node-reproducibility
> - old-guix-wip-file-offset-bits-64-sledgehammer
> - r-team
> - r-updates
> - rust-team
>
> If anyone knows if any of these branches can be deleted, please go
> ahead. If they do want merging, please open a "Request for merging"
> issue. For the ones that still have changes, but we're not looking to
> merge right now, I think the easist thing to do is rename them adding
> the wip- prefix.
I've added wip- prefixes to the following 4 branches now, mostly as
these were the oldest ones processed by data.qa:
- go-team
- node-reproducibility
- node-18-updates
- r-team
Maybe we can look again at the other branches once the merge backlog has
gone down a bit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2024-06-19 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 9:36 Cleaning up branches on savannah Christopher Baines
2024-06-07 12:46 ` Lars-Dominik Braun
2024-06-07 13:43 ` Mark H Weaver
2024-06-07 14:00 ` Christopher Baines
2024-06-11 15:16 ` Mark H Weaver
2024-06-12 9:11 ` Andreas Enge
2024-06-19 14:00 ` Christopher Baines
2024-06-19 14:03 ` Christopher Baines [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6dp3u7m.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.