all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Z572 <zhengjunjie@iscas.ac.cn>
To: Greg Hogan <code@greghogan.com>
Cc: 74440@debbugs.gnu.org
Subject: [bug#74440] [PATCH 0/2] Add C/C++ team.
Date: Sun, 24 Nov 2024 09:43:58 +0800	[thread overview]
Message-ID: <87wmgt4d9d.fsf@iscas.ac.cn> (raw)
In-Reply-To: <cover.1732050358.git.code@greghogan.com> (Greg Hogan's message of "Tue, 19 Nov 2024 21:22:23 +0000")

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

Greg Hogan <code@greghogan.com> writes:

> Let's build a C/C++ team. All are welcome to join!
>
> The dual-language "C/C++" is used as descriptor and the simpler "c++"
> as the team name for use with the etc/teams.scm commands.
>
> Greg Hogan (2):
>   teams: Add C/C++ team.
>   teams: Add entry for Greg Hogan.
>
>  etc/teams.scm | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>
>
> base-commit: 20ecc8b5a995dd782891dcfe213dd3c67295fe30

I think you still need to discuss it on guix-devel

see https://guix.gnu.org/manual/devel/en/html_node/Teams.html

     One or more people may propose the creation of a new team by reaching
  out to the community by email at <guix-devel@gnu.org>, clarifying the
  intended scope and purpose.  When consensus is reached on the creation
  of this team, someone with commit access formalizes its creation by
  adding it and its initial members to ‘etc/teams.scm’.



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

  parent reply	other threads:[~2024-11-24  1:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 21:22 [bug#74440] [PATCH 0/2] Add C/C++ team Greg Hogan
2024-11-19 21:33 ` [bug#74440] [PATCH 1/2] teams: " Greg Hogan
2024-11-19 21:33 ` [bug#74440] [PATCH 2/2] teams: Add entry for Greg Hogan Greg Hogan
2024-11-24  1:43 ` Z572 [this message]
2024-11-25 13:45   ` [bug#74440] [PATCH 0/2] Add C/C++ team Greg Hogan

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=87wmgt4d9d.fsf@iscas.ac.cn \
    --to=zhengjunjie@iscas.ac.cn \
    --cc=74440@debbugs.gnu.org \
    --cc=code@greghogan.com \
    /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.