From: Greg Troxel <gdt@lexort.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: Andy Wingo <wingo@pobox.com>,
guile-sources@gnu.org, guile-user <guile-user@gnu.org>,
Maxime Devos <maximedevos@telenet.be>,
guile-devel <guile-devel@gnu.org>
Subject: Re: GNU Guile 3.0.8 released
Date: Fri, 11 Feb 2022 20:28:27 -0500 [thread overview]
Message-ID: <rmi7da0j2kk.fsf@s1.lexort.com> (raw)
In-Reply-To: <CA+XASoUAfqwZnUD42OegS2Aza+MqiYtK2F982EDcyVqx0vGBfQ@mail.gmail.com> ("Aleix Conchillo Flaqué"'s message of "Fri, 11 Feb 2022 09:14:15 -0800")
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Aleix Conchillo Flaqué <aconchillo@gmail.com> writes:
> On Fri, Feb 11, 2022 at 3:05 AM Maxime Devos <maximedevos@telenet.be> wrote:
>
>> Andy Wingo schreef op vr 11-02-2022 om 08:47 [+0100]:
>> > We are delighted to announce GNU Guile release 3.0.8, the latest in the
>> [...]
>> > The Guile 3.0.8 release mixes maintenance and optimizations [...]
>>
>>
> Am I the only one who has not received the announcement?
I got the announcement but it was filed to spam because of a rule
KAM_MAILSPLOIT (KAM ruleset for spamassassin), because there were two
From: headers. I have reported this ruleset false positive.
Andy: Perhaps resend, with only one From: header.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2022-02-12 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 7:47 GNU Guile 3.0.8 released Andy Wingo
2022-02-11 11:05 ` Maxime Devos
2022-02-11 17:14 ` Aleix Conchillo Flaqué
2022-02-11 18:03 ` Ricardo Wurmus
2022-02-12 1:28 ` Greg Troxel [this message]
2022-02-12 2:04 ` Aleix Conchillo Flaqué
2022-02-11 14:34 ` [PP?] " Olivier Dion via Developers list for Guile, the GNU extensibility library
-- strict thread matches above, loose matches on Subject: below --
2022-02-12 13:54 Andy Wingo
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=rmi7da0j2kk.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--cc=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
--cc=wingo@pobox.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).