From: Mark Wielaard <mark@klomp.org>
To: Sam James <sam@gentoo.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Jakub Jelinek <jakub@redhat.com>, Andreas Schwab <schwab@suse.de>,
Joseph Myers <joseph@codesourcery.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: dmarc, dkim and From rewriting
Date: Wed, 6 Sep 2023 20:49:40 +0200 [thread overview]
Message-ID: <20230906184940.GA19396@gnu.wildebeest.org> (raw)
In-Reply-To: <20230904084839.GA19773@gnu.wildebeest.org>
Hi,
On Mon, Sep 04, 2023 at 10:48:39AM +0200, Mark Wielaard wrote:
> On irc people also seemed really enthousiastic about this. I did some
> more analysis on the libc-alpha messages sent this year [*] and I
> think things will work out fine. So I propose we just try it out.
>
> Lets flip the switch (there are actually multiple switches, I'll
> document them in the bug) on Wednesday 18:00 UTC.
This is now active. The mailinglist settings are as described in
https://sourceware.org/bugzilla/show_bug.cgi?id=29713#c45
> Then we can monitor
> things and analyze whether things worked as expected after 48 hours at
> the Overseers Open Office Hour this Friday at 18:00 UTC in #overseers
> on irc.libera.chat.
>
> That might also be a good time to discuss any other glibc service
> blockers. For example, it would be great to figure out how to use
> builder.sourceware.org workers for patchwork.sourceware.org testing.
And please feel free to drop by in #overseers whenever you like and/or
to report issues through mail or bugzilla as described at:
https://sourceware.org/mission.html#organization
Cheers,
Mark
> [*] https://sourceware.org/bugzilla/show_bug.cgi?id=29713#c44
next prev parent reply other threads:[~2023-09-06 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 8:48 Mark Wielaard
2023-09-06 18:49 ` Mark Wielaard [this message]
2023-09-08 17:21 ` Mark Wielaard
[not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` [Action Required] glibc decision to use CTI services Alexandre Oliva
2023-08-30 17:31 ` Joseph Myers
2023-08-31 19:59 ` Paul Eggert
2023-09-01 6:03 ` Sam James
2023-09-01 8:55 ` Florian Weimer
2023-09-01 9:02 ` Sam James
2023-09-01 9:21 ` dmarc, dkim and From rewriting Mark Wielaard
2023-09-01 11: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=20230906184940.GA19396@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
/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).