From: Ada Stevenson <adanskana@gmail.com>
To: Andy Tai <atai@atai.org>, guix-devel@gnu.org
Subject: Re: status of (future of) Guix QA
Date: Tue, 26 Dec 2023 05:44:16 +0000 [thread overview]
Message-ID: <57625c72-9b46-b75e-e5a7-0506744032e1@gmail.com> (raw)
In-Reply-To: <CAJsg1E-XM3AwrzujvgU7bmHt6FF+n8Fqx2t+uXUWetA6Lc-iTQ@mail.gmail.com>
Hi,
On 12/22/23 8:11 PM, Andy Tai wrote:
> Curious of the status of the future of Guix QA as package definition
> contributors rely on it for updating packages (sending patches to get
> accepted/committed) in guix...
I'm curious too. Did anything come of the discussion a few weeks ago?
Ada (adanksa)
next prev parent reply other threads:[~2023-12-26 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 20:11 status of (future of) Guix QA Andy Tai
2023-12-26 5:44 ` Ada Stevenson [this message]
2023-12-26 14:45 ` Jing Luo
2023-12-26 20:41 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-27 5:34 ` Jing Luo
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=57625c72-9b46-b75e-e5a7-0506744032e1@gmail.com \
--to=adanskana@gmail.com \
--cc=atai@atai.org \
--cc=guix-devel@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 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).