From: Harald Koenig <harald@mailbox.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: xorg-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org,
board <board@foundation.x.org>,
members@x.org, amd-gfx@lists.freedesktop.org,
mesa-dev@lists.freedesktop.org, events@lists.x.org,
Ricardo Garcia <rgarcia@igalia.com>,
freedreno@lists.freedesktop.org,
libre-soc-dev@lists.libre-soc.org
Subject: Re: 2023 X.Org Foundation Membership deadline for voting in the election
Date: Mon, 17 Apr 2023 20:48:09 +0200 [thread overview]
Message-ID: <ZD2UabVlQOBVaVRO@hl.fritz.box> (raw)
In-Reply-To: <20230417124502.GB19964@pendragon.ideasonboard.com>
On Apr 17, Laurent Pinchart wrote:
> I don't know if I'm the only one affected by this issue, but I've just
> received today two months of e-mails from x.org, including all the
> reminders aboud membership renewal and election nomination period. This
> isn't the first time this happens, and the last time I was told there
> was no automated process to quick the mail queues when errors happen,
> making mails pile up forever on x.org's side until someone handles it
> manually. This is something you really want to automate, or at least
> monitored.
same here for me: looking into the mail header,
both mails were stuck on server "gabe.freedesktop.org"
Received: from gabe.freedesktop.org (localhost [127.0.0.1])
by gabe.freedesktop.org (Postfix) with ESMTP id BD01310E459;
Mon, 17 Apr 2023 11:42:45 +0000 (UTC)
X-Original-To: events@lists.x.org
Delivered-To: events@lists.x.org
Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56])
by gabe.freedesktop.org (Postfix) with ESMTPS id 6C54510E162;
Wed, 15 Feb 2023 15:58:10 +0000 (UTC)
and
Received: from gabe.freedesktop.org (localhost [127.0.0.1])
by gabe.freedesktop.org (Postfix) with ESMTP id 6735010E46D;
Mon, 17 Apr 2023 11:42:45 +0000 (UTC)
X-Original-To: events@lists.x.org
Delivered-To: events@lists.x.org
Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56])
by gabe.freedesktop.org (Postfix) with ESMTPS id 98DB48953E;
Mon, 13 Mar 2023 15:23:02 +0000 (UTC)
Harald
--
"I hope to die ___ _____
before I *have* to use Microsoft Word.", 0--,| /OOOOOOO\
Donald E. Knuth, 02-Oct-2001 in Tuebingen. <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
\/\/\/\/\/\/\/\/\/
Harald Koenig // / \\ \
harald.koenig@mailbox.org ^^^^^ ^^^^^
prev parent reply other threads:[~2023-04-19 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 15:58 2023 X.Org Foundation Membership deadline for voting in the election Ricardo Garcia
2023-03-13 15:22 ` Ricardo Garcia
2023-04-17 12:45 ` Laurent Pinchart
2023-04-17 18:48 ` Harald Koenig [this message]
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=ZD2UabVlQOBVaVRO@hl.fritz.box \
--to=harald@mailbox.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=board@foundation.x.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=events@lists.x.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=libre-soc-dev@lists.libre-soc.org \
--cc=members@x.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rgarcia@igalia.com \
--cc=wayland-devel@lists.freedesktop.org \
--cc=xorg-devel@lists.freedesktop.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