From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 58365@debbugs.gnu.org
Subject: [bug#58365] [PATCH 0/6] Support #:tests? in guile-build-system
Date: Mon, 20 Nov 2023 01:41:10 +0100 [thread overview]
Message-ID: <7f81995d-b3a1-fa59-5651-86f5768d5797@telenet.be> (raw)
In-Reply-To: <8a38968e-e3bb-9444-8b98-756f0178fe42@telenet.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 324 bytes --]
(Some context I forgot to include:)
Around the same time at the last previous message on technical matters
(https://issues.guix.gnu.org/58365#9), Ludo' sent a PM on some
non-technical matters, and I answered to the PM instead of 58365,
leaving the technical matters message unreplied. So, now, at last, a reply.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2023-11-20 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 20:47 [bug#58365] [PATCH 0/6] Support #:tests? in guile-build-system Maxime Devos
2022-10-07 20:53 ` [bug#58365] [PATCH 1/6] gnu: Add guile-test-driver Maxime Devos
2022-10-07 20:53 ` [bug#58365] [PATCH 2/6] build-system/guile: Run SRFI-64 tests Maxime Devos
2022-10-07 20:53 ` [bug#58365] [PATCH 3/6] guile-ffi-fftw: Respect #:tests? Maxime Devos
2022-10-07 20:53 ` [bug#58365] [PATCH 4/6] guile-ffi-fftw: Modernise style Maxime Devos
2022-10-07 20:53 ` [bug#58365] [PATCH 5/6] guile-ffi-fftw: Update to new Guile version Maxime Devos
2022-10-07 20:53 ` [bug#58365] [PATCH 6/6] guile-ac-d-bus: Don't duplicate 'check' phase Maxime Devos
2022-10-18 12:36 ` [bug#58365] [PATCH 0/6] Support #:tests? in guile-build-system Ludovic Courtès
2022-10-18 13:30 ` Maxime Devos
2022-10-18 15:44 ` Ludovic Courtès
2023-11-20 0:34 ` Maxime Devos
2023-11-20 0:41 ` Maxime Devos [this message]
2023-12-03 9:17 ` Efraim Flashner
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=7f81995d-b3a1-fa59-5651-86f5768d5797@telenet.be \
--to=maximedevos@telenet.be \
--cc=58365@debbugs.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.