From: Andrew Pinski <pinskia@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Sam James via Libc-alpha <libc-alpha@sourceware.org>,
Jakub Jelinek <jakub@redhat.com>,
Andreas Schwab <schwab@suse.de>, Mark Wielaard <mark@klomp.org>,
Joseph Myers <joseph@codesourcery.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Fri, 1 Sep 2023 02:03:35 -0700 [thread overview]
Message-ID: <CA+=Sn1npmF58A7VqyE_nkeqFMvsUDGaiF_S6o+dO1JU=peJZ6w@mail.gmail.com> (raw)
In-Reply-To: <87fs3yp91h.fsf@oldenburg.str.redhat.com>
On Fri, Sep 1, 2023 at 1:56 AM Florian Weimer via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> * Sam James via Libc-alpha:
>
> > As far as I've seen, the sourceware overseers handle requests
> > promptly. Is there something we've asked them to do which they've
> > been unable to fulfill?
>
> Removing the From: header rewriting from the mailing lists, including
> libc-alpha. With the current list configuration, “git am” often does
> not produce correct results.
Isn't that due to security (anti-spam) measures of many ISPs?
How can someone solve that issue without the rewriting due to mailing
lists and security measures not going hand in hand these days?
Thanks,
Andrew
>
> Thanks,
> Florian
>
next prev parent reply other threads:[~2023-09-01 9:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` 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
2023-09-01 9:03 ` Andrew Pinski [this message]
2023-09-01 11:49 ` [Action Required] glibc decision to use CTI services Florian Weimer
2023-09-01 13:32 ` Frank Ch. Eigler
2023-09-01 12:30 ` Siddhesh Poyarekar
2023-09-01 14:54 ` Paul Eggert
2023-09-01 16:08 ` Siddhesh Poyarekar
2023-09-01 15:01 ` Sam James
2023-09-01 16:19 ` Frank Ch. Eigler
2023-09-01 16:30 ` Siddhesh Poyarekar
2023-09-02 18:25 ` Mark Wielaard
2023-09-01 9:08 ` Mark Wielaard
2023-09-03 6:31 ` Alexandre Oliva
2023-09-27 13:49 ` Carlos O'Donell
2023-10-04 0:09 ` Paul Eggert
2023-09-01 15:09 ` Alexandre Oliva
2023-09-27 13:50 ` Carlos O'Donell
2024-02-13 0:43 ` Carlos O'Donell
2024-02-19 21:22 ` Alexandre Oliva
2024-02-19 22:03 ` DJ Delorie
2024-02-20 1:49 ` Mark Wielaard
2024-02-20 3:01 ` Alexandre Oliva
2023-08-31 8:37 ` Mark Wielaard
2023-09-01 15:08 ` Alexandre Oliva
2023-08-31 10:34 ` Florian Weimer
2023-09-04 6:09 ` Alexandre Oliva
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='CA+=Sn1npmF58A7VqyE_nkeqFMvsUDGaiF_S6o+dO1JU=peJZ6w@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=maxim.kuvyrkov@linaro.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).