all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>,
	Mathieu Othacehe <othacehe@gnu.org>
Cc: 60540@debbugs.gnu.org
Subject: [bug#60540] teams: Add scope for Embedded / Bootstrap
Date: Mon, 15 May 2023 20:54:11 +0200	[thread overview]
Message-ID: <87ednh2zos.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87lelzzlmt.fsf@contorta>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hi everyone,

Vagrant Cascadian <vagrant@debian.org> writes:

> New patch attached which also splits the teams.
>
> They could still probably significantly benefit from
> descriptions... though I haven't heard much of anything weighed in on
> that from the discussion on guix-devel.
>
> live well,
>   vagrant
> From 0ae1c6951bcfd3c1a83e8a86adcbc6afae122c01 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@debian.org>
> Date: Wed, 18 Jan 2023 11:17:36 -0800
> Subject: [PATCH] teams: Split Embedded and Bootstrap into separate teams.
>
> * etc/teams.scm.in (embedded-bootstrap): Replace by two separate teams.
>   (embedded): New variable.
>   (bootstrap): New variable.
>   Adjust membership to use new teams.

Any news about this patch?

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  reply	other threads:[~2023-05-15 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  5:53 [bug#60540] teams: Add scope for Embedded / Bootstrap Vagrant Cascadian
2023-01-08 13:43 ` Mathieu Othacehe
2023-01-10 23:21   ` Vagrant Cascadian
2023-01-18 19:30   ` Vagrant Cascadian
2023-05-15 18:54     ` Josselin Poiret via Guix-patches via [this message]
2023-05-15 19:21       ` Vagrant Cascadian
2023-05-24 22:55         ` bug#60540: " Vagrant Cascadian

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=87ednh2zos.fsf@jpoiret.xyz \
    --to=guix-patches@gnu.org \
    --cc=60540@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=othacehe@gnu.org \
    --cc=vagrant@debian.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.