From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Philip McGrath <philip@philipmcgrath.com>,
59322@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope.
Date: Sat, 19 Nov 2022 08:54:55 +0100 [thread overview]
Message-ID: <106658bfff0dbda421cda6c45d76a4d3237d47e1.camel@gmail.com> (raw)
In-Reply-To: <2144765.irdbgypaU6@bastet>
Am Freitag, dem 18.11.2022 um 14:33 -0500 schrieb Philip McGrath:
> I could certainly imagine having a Chez team that doesn't necessarily
> care about Racket. Likewise, in both languages, I imagine there could
> be people interested in packages that use the language but who
> wouldn't necessarily be interested in the packaging of the compilers
> and run-time systems themselves.
> But, since no one else has signed on and I've made the majority of
> changes to both files in the last two years, designing a more fine-
> grained team structure seemed premature.
I can see where you're coming from, but my personal opinion is that
merging these "two" teams now might discourage us from splitting them
later. In my humble opinion, adding a chez team with you as sole
member wouldn't hurt for the time being.
Cheers
next prev parent reply other threads:[~2022-11-19 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:36 [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Philip McGrath
2022-11-16 21:39 ` [bug#59322] [PATCH 1/2] " Philip McGrath
2022-11-17 7:30 ` Liliana Marie Prikler
2022-11-18 0:45 ` [bug#59322] [PATCH v2 0/4] " Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 1/4] " Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 2/4] gnu: chez-scheme-for-racket: Support riscv64 Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 3/4] gnu: racket-vm-cs: Avoid duplicate work Philip McGrath
2022-11-18 0:45 ` [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope Philip McGrath
2022-11-18 7:01 ` Liliana Marie Prikler
2022-11-18 8:26 ` zimoun
2022-11-18 19:23 ` Liliana Marie Prikler
2022-11-18 19:33 ` Philip McGrath
2022-11-19 7:54 ` Liliana Marie Prikler [this message]
2022-11-19 23:52 ` Philip McGrath
2022-11-20 1:49 ` Liliana Marie Prikler
2022-11-23 18:44 ` [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Ludovic Courtès
2022-11-21 16:50 ` [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope zimoun
2022-12-01 21:08 ` bug#59322: [PATCH 0/2] gnu: racket: Update to 8.7 Ludovic Courtès
2022-11-16 21:39 ` [bug#59322] [PATCH 2/2] gnu: racket-vm-cs: Avoid duplicate work Philip McGrath
2022-12-04 13:25 ` [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Enrico Schwass via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=106658bfff0dbda421cda6c45d76a4d3237d47e1.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=59322@debbugs.gnu.org \
--cc=philip@philipmcgrath.com \
--cc=zimon.toutoune@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).