From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: Maxime Devos <maximedevos@telenet.be>, guile-devel@gnu.org
Subject: Re: automake test driver for Guile scheme patch review
Date: Wed, 22 Nov 2023 23:19:55 -0500 [thread overview]
Message-ID: <87il5t85jo.fsf@gmail.com> (raw)
In-Reply-To: <8734wy3e35.fsf@ngyro.com> (Timothy Sample's message of "Tue, 21 Nov 2023 17:02:06 -0600")
Hi,
Timothy Sample <samplet@ngyro.com> writes:
> Hello,
>
> [Dropping Karl since we are no longer discussing Automake maintenance.]
>
> Maxime Devos <maximedevos@telenet.be> writes:
>
>> [What about] discoverability, ease of updating the test driver,
>> clarity, unbundling and the goals of Freja Nordsiek?
>
> Maybe Guile should adopt the script as ‘guild test-am’ or somesuch.
> Mathieu assigned copyright to the FSF for the Automake patch and I
> believe Maxim would be willing to do the same for the more recent
> patches.
I think having such a guild command would be nice for reuse. I'm happy
to assign my copyright to the FSF, although that's not strictly needed
anymore as pointed to Maxime.
> If there’s interest and someone willing to commit the change, I
> volunteer to integrate the script. I can add a node in the manual after
> “4.8 Distributing Guile Code” called “Testing Guile Code” that links to
> Maxim’s forthcoming SRFI 64 documentation and explains how to use the
> script with Automake.
>
> Thoughts?
Sounds good to me! Thanks for the initiative.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-11-23 4:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 17:17 automake test driver for Guile scheme patch review Karl Berry
2023-11-19 19:55 ` Freja Nordsiek
2023-11-19 23:43 ` Maxime Devos
2023-11-20 16:16 ` Timothy Sample
2023-11-21 17:33 ` Maxime Devos
2023-11-21 22:57 ` Maxime Devos
2023-11-21 23:02 ` Timothy Sample
2023-11-21 23:08 ` Maxime Devos
2023-11-23 4:19 ` Maxim Cournoyer [this message]
2023-11-21 21:45 ` Karl Berry
2023-11-22 20:05 ` Freja Nordsiek
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il5t85jo.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=samplet@ngyro.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.
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).