unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: guile-devel@gnu.org
Subject: Re: GNU Guile 3.0.8 released
Date: Sat, 12 Feb 2022 09:01:28 +0100	[thread overview]
Message-ID: <YgdpWGulSnJ2fPvo@tuxteam.de> (raw)
In-Reply-To: <20220211185150.77964d21102c9dcf2253d2b4@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

On Fri, Feb 11, 2022 at 06:51:50PM +0000, Chris Vine wrote:
> On Fri, 11 Feb 2022 19:03:17 +0100
> Ricardo Wurmus <rekado@elephly.net> wrote:
> > 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?
> > 
> > No.  I also haven’t received it.
> 
> I didn't receive it either, on either guile-user or guile-devel.  It
> looks as if something may be amiss with the mailing list servers.

FWIW, I did receive it, and the To: header field looks innocent enough:

  To: guile-user@gnu.org, guile-sources@gnu.org, guile-devel@gnu.org, info-gnu@gnu.org

Here are the more envelope-ish headers:

  From guile-devel-bounces+tomas=tuxteam.de@gnu.org Fri Feb 11 08:48:40 2022
  Return-path: <guile-devel-bounces+tomas=tuxteam.de@gnu.org>
  Envelope-to: tomas@tuxteam.de
  Delivery-date: Fri, 11 Feb 2022 08:48:40 +0100
  Received: from lists.gnu.org ([209.51.188.17])
          by mail.tuxteam.de with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
          (Exim 4.94.2)
          (envelope-from <guile-devel-bounces+tomas=tuxteam.de@gnu.org>)
          id 1nIQfY-0000rR-Jv
          for tomas@tuxteam.de; Fri, 11 Feb 2022 08:48:40 +0100

...so it seems it came through guile-devel@

I haven't checked whether the DKIM signature is good, though. So maybe...

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-02-12  8:01 UTC|newest]

Thread overview: 11+ 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-11 18:51       ` Chris Vine
2022-02-12  8:01         ` tomas [this message]
2022-02-12 10:15           ` Alexey Abramov
2022-02-12  1:28     ` Greg Troxel
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=YgdpWGulSnJ2fPvo@tuxteam.de \
    --to=tomas@tuxteam.de \
    --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).