all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: indieterminacy <indieterminacy@libre.brussels>
To: Greg Hogan <code@greghogan.com>
Cc: "Liliana Marie Prikler" <liliana.prikler@gmail.com>,
	guix-devel <guix-devel@gnu.org>,
	"Efraim Flashner" <efraim@flashner.co.il>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Creating a C/C++ team?
Date: Fri, 06 Dec 2024 08:27:25 +0000	[thread overview]
Message-ID: <71c22e336e6460d1a3521e0b81ac12e7@libre.brussels> (raw)
In-Reply-To: <CA+3U0Zkt3zLggyu=bUKDdr_OjK-NfrZoSvb_HzG4+J+dB8mBYQ@mail.gmail.com>

Hello,

Is it too late to have this team having an id name 'cpp' rather than 
'c++'?
As a fan of regex its use of the almighty plus sign has wrankled me.
Also, as an outsider Ive always considered cpp to be representative of 
both C and C++, rather than a subset.

Thanks,

Jonathan

On 2024-12-05 23:35, Greg Hogan wrote:
> On Fri, Nov 29, 2024 at 4:35 AM Liliana Marie Prikler
> 
> ...
> 
> $ ./etc/teams.scm show c++
> id: c++
> name: C/C++ team
> description: C and C++ libraries and tools and the CMake build system.
> + Note that updates to fundamental packages are the competency of the
> + core-packages team.
> scope:
> + gnu/build-system/cmake.scm
> + gnu/build/cmake-build-system.scm
> + gnu/packages/c.scm
> + gnu/packages/cmake.scm
> + gnu/packages/cpp.scm
> + gnu/packages/ninja.scm
> + gnu/packages/valgrind.scm


  reply	other threads:[~2024-12-06  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 18:27 Creating a C/C++ team? Greg Hogan
2024-11-28  8:26 ` Ludovic Courtès
2024-11-29  9:36 ` Liliana Marie Prikler
2024-11-30 15:19   ` Ludovic Courtès
2024-12-01 10:02   ` Efraim Flashner
2024-12-05 23:35   ` Greg Hogan
2024-12-06  8:27     ` indieterminacy [this message]
2024-12-06  9:39       ` Andreas Enge
2024-12-06 19:45     ` Liliana Marie Prikler
2024-12-14 23:56     ` Ludovic Courtès

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=71c22e336e6460d1a3521e0b81ac12e7@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=code@greghogan.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=ludo@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.