all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>,
	Philip McGrath <philip@philipmcgrath.com>,
	59322@debbugs.gnu.org
Subject: [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope.
Date: Fri, 18 Nov 2022 20:23:23 +0100	[thread overview]
Message-ID: <4800d2fda3378f087fc1674ee9389f9c62d943f2.camel@gmail.com> (raw)
In-Reply-To: <867czsk6rw.fsf@gmail.com>

Am Freitag, dem 18.11.2022 um 09:26 +0100 schrieb zimoun:
> Hi,
> 
> On Fri, 18 Nov 2022 at 08:01, Liliana Marie Prikler
> <liliana.prikler@ist.tugraz.at> wrote:
> 
> > > -        #:scope (list "gnu/packages/racket.scm")))
> > > +        #:scope (list "gnu/packages/chez.scm"
> > > +                      "gnu/packages/racket.scm")))
> > 
> > I'm not sure whether this accurately captures the intent of teams. 
> > Yes, chez-scheme is required in Racket's bootstrap, but the only
> > "legal" changes to Racket's variant also affect racket.scm.  On the
> > other hand, the Racket team would weigh in on changes that only
> > affect the Chez side, which imho is unwarranted.
> 
> Why not?  Considering the only person part of the Racket team is
> Philip, the false-positive seems acceptable, no?
Given that folks tune out the main mailing list 

> BTW, Liliana, since you are often reviewing these patches, why not
> also add you as part of the Racket team?
To be frank, I only review them with respect to Guix coding guidelines.
I have no idea how Racket itself works – if I did, I would already have
fixed some annoyances with its packaging – and I fear that despite all
my efforts Philip might be the only one who truly understands what's
going on.

Cheers




  reply	other threads:[~2022-11-18 19:24 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 [this message]
2022-11-18 19:33           ` Philip McGrath
2022-11-19  7:54             ` Liliana Marie Prikler
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4800d2fda3378f087fc1674ee9389f9c62d943f2.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 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.