From: Daniel Tornabene <d.t.peters777@gmail.com>
To: guile-devel@gnu.org
Subject: apologies on the previous message, I had not checked the bug tracker first
Date: Fri, 31 Jul 2020 12:25:39 -0500 [thread overview]
Message-ID: <CAMo=-SBm59N1GtTE1_WqkqK3GpPxmHi_dMGs0pWthv_iVaqQmw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
I sent a message yesterday on this bug
https://sourceware.org/bugzilla/show_bug.cgi?id=21104 but had neglected to
check before posting. My apologies for the noise.
And thank you to Ludovic and Doug Evans for their work on the patch fixing
said bug. Really excited to have my code run on Guile 3.0 as soon as
possible.
[-- Attachment #2: Type: text/html, Size: 435 bytes --]
reply other threads:[~2020-07-31 17:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMo=-SBm59N1GtTE1_WqkqK3GpPxmHi_dMGs0pWthv_iVaqQmw@mail.gmail.com' \
--to=d.t.peters777@gmail.com \
--cc=guile-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.
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).