From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Bruno Victal <mirai@makinata.eu>
Cc: 64449@debbugs.gnu.org
Subject: [bug#64449] [PATCH 0/4] Fix lua-cqueues build failure.
Date: Wed, 30 Aug 2023 15:57:07 -0400 [thread overview]
Message-ID: <87sf805mng.fsf_-_@gmail.com> (raw)
In-Reply-To: <6481d9abe50694624c0f63d3abf8f4348deac449.1688423261.git.mirai@makinata.eu> (Bruno Victal's message of "Mon, 3 Jul 2023 23:28:43 +0100")
Hi,
Bruno Victal <mirai@makinata.eu> writes:
> * gnu/packages/lua.scm (make-lua-cqueues): Use G-Expressions.
> Drop obsolete phases.
LGTM.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-08-30 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 22:26 [bug#64449] [PATCH 0/4] Fix lua-cqueues build failure Bruno Victal
2023-07-03 22:28 ` [bug#64449] [PATCH 1/4] gnu: lua-ossl: Update to 20220711 Bruno Victal
2023-08-30 19:54 ` [bug#64449] [PATCH 0/4] Fix lua-cqueues build failure Maxim Cournoyer
2023-07-03 22:28 ` [bug#64449] [PATCH 2/4] gnu: lua-ossl: Use G-expressions Bruno Victal
2023-08-30 19:55 ` [bug#64449] [PATCH 0/4] Fix lua-cqueues build failure Maxim Cournoyer
2023-07-03 22:28 ` [bug#64449] [PATCH 3/4] gnu: lua-cqueues: Update to 20200726 Bruno Victal
2023-08-30 19:57 ` [bug#64449] [PATCH 0/4] Fix lua-cqueues build failure Maxim Cournoyer
2023-07-03 22:28 ` [bug#64449] [PATCH 4/4] gnu: lua-cqueues: Refactor package definition Bruno Victal
2023-08-30 19:57 ` Maxim Cournoyer [this message]
2023-08-31 15:03 ` [bug#64449] [PATCH v2 1/4] gnu: lua-ossl: Update to 20220711 Bruno Victal
2023-08-31 15:03 ` [bug#64449] [PATCH v2 2/4] gnu: lua-ossl: Use G-expressions Bruno Victal
2023-08-31 15:03 ` [bug#64449] [PATCH v2 3/4] gnu: lua-cqueues: Update to 20200726 Bruno Victal
2023-08-31 15:03 ` [bug#64449] [PATCH v2 4/4] gnu: lua-cqueues: Refactor package definition Bruno Victal
2023-10-09 0:51 ` [bug#64449] [PATCH 0/4] Fix lua-cqueues build failure Bruno Victal
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=87sf805mng.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=64449@debbugs.gnu.org \
--cc=mirai@makinata.eu \
/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).