From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: Message not distributed over libc-alpha
Date: Tue, 7 Jun 2022 09:17:46 +0200 [thread overview]
Message-ID: <Yp77msPVS4/JfPvy@wildebeest.org> (raw)
In-Reply-To: <87leu9otbv.fsf@oldenburg.str.redhat.com>
Hi Florian,
On Tue, Jun 07, 2022 at 08:56:04AM +0200, Florian Weimer via Overseers wrote:
> This message
>
> From: Florian Weimer <fweimer@redhat.com>
> Subject: Re: [PATCH v2] elf: Remove one-default-version check when searching
> an unversioned symbol
> To: Fangrui Song <maskray@google.com>
> Cc: Fangrui Song via Libc-alpha <libc-alpha@sourceware.org>
> Date: Tue, 31 May 2022 21:39:01 +0200 (6 days, 11 hours, 13 minutes ago)
> Message-ID: <87leuhpk4q.fsf@oldenburg.str.redhat.com>
>
> was not distributed via libc-alpha and did not end up in the archives.
As far as I can see this message was distributed via libc-alpha and
did end up in the archives:
https://sourceware.org/pipermail/libc-alpha/2022-May/139228.html
> Could you please have a look if you can find any traces in the logs?
> Maybe the problem is on my end.
It also should have been delivered to you:
May 31 19:39:31 server2 postfix/cleanup[180248]: B3EB5396E06E: message-id=<87leuhpk4q.fsf@oldenburg.str.redhat.com>
May 31 19:39:31 server2 postfix/qmgr[2143219]: B3EB5396E06E: from=<libc-alpha-bounces+fweimer=redhat.com@sourceware.org>, size=12883, nrcpt=1 (queue active)
May 31 19:39:32 server2 postfix/smtp[139826]: B3EB5396E06E: to=<fweimer@redhat.com>, relay=us-smtp-inbound-1.mimecast.com[207.211.30.221]:25, delay=1, delays=0.1/0/0.25/0.66, dsn=2.0.0, status=sent (250 SmtpThread-7853133-1654025972712@us-mta-435.us.mimecast.lan Received OK [c9an2lwjOZqdrO1WtxvhUg.us435])
Hope that helps.
Cheers,
Mark
next prev parent reply other threads:[~2022-06-07 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 6:56 Florian Weimer
2022-06-07 7:17 ` Mark Wielaard [this message]
2022-06-07 7:52 ` Florian Weimer
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=Yp77msPVS4/JfPvy@wildebeest.org \
--to=mark@klomp.org \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.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).