all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, guile-devel@gnu.org
Subject: Re: Resurrecting top-notch continuous integration for Guile
Date: Sun, 29 Jan 2023 10:34:40 -0800	[thread overview]
Message-ID: <CAFHYt573R7oWLpDu1m-1=bVDF_yD9q2OjVUpD_mxKFn0qAp3Ug@mail.gmail.com> (raw)
In-Reply-To: <87lell2qgc.fsf@inria.fr>

Hi Ludo'

On Sun, Jan 29, 2023 at 9:37 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> I hereby ask fellow Guix hackers to voice any
> concerns they may have regarding this use of project resources.

I am not a Guix hacker (although maybe every user is one too) and, as
a newbie, I cannot speak for the group but the Guix project is built
on Guile and depends on Guile functioning properly. I cannot imagine
any opposition whatsoever.

The way I see it, Guixers are more likely to celebrate your proposal
as a welcome milestone in the continuous evolution of Guix and Nix.

> If there are no objections, I’ll merge this
> branch into “main”.

As it stands, Guix owes a profound debt of gratitude to Guile and its
developers. There is no reason to wait.

Thank you for your expert stewardship in designing the OS we all love so much!

Kind regards
Felix


  reply	other threads:[~2023-01-29 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 17:36 Resurrecting top-notch continuous integration for Guile Ludovic Courtès
2023-01-29 18:34 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-01-29 21:02 ` Tobias Geerinckx-Rice
2023-02-06 16:58 ` Ludovic Courtès
2023-02-06 20:55   ` Maxim Cournoyer

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='CAFHYt573R7oWLpDu1m-1=bVDF_yD9q2OjVUpD_mxKFn0qAp3Ug@mail.gmail.com' \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=guile-devel@gnu.org \
    --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.