From: Vagrant Cascadian <vagrant@debian.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 60540@debbugs.gnu.org
Subject: [bug#60540] teams: Add scope for Embedded / Bootstrap
Date: Tue, 10 Jan 2023 15:21:12 -0800 [thread overview]
Message-ID: <87sfgim0wn.fsf@contorta> (raw)
In-Reply-To: <87lemduopj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On 2023-01-08, Mathieu Othacehe wrote:
>> (define-team embedded-bootstrap
>> (team 'embedded-bootstrap
>> - #:name "Embedded / Bootstrap"))
>> + #:name "Embedded / Bootstrap"
>> + #:scope (list "gnu/packages/bootloaders.scm"
>> + "gnu/packages/firmware.scm"
>> + "gnu/packages/mes.scm")))
>
> Seems fine.
>
> I think we could have two distinct teams here: embedded and
> bootstrap. There are quite a few people, like me, following closely the
> embedded part, but not so closely the bootstrap part.
Yeah, I think they should be split so started a thread on guix-devel:
https://lists.gnu.org/archive/html/guix-devel/2023-01/msg00048.html
But I also wanted to start by keeping this patch simple. Although it
could really use a description too ...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-01-10 23:22 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 [this message]
2023-01-18 19:30 ` Vagrant Cascadian
2023-05-15 18:54 ` Josselin Poiret via Guix-patches via
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=87sfgim0wn.fsf@contorta \
--to=vagrant@debian.org \
--cc=60540@debbugs.gnu.org \
--cc=othacehe@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.