public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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: dmarc, dkim and From rewriting
Date: Fri, 1 Sep 2023 11:21:33 +0200	[thread overview]
Message-ID: <20230901092133.GB22481@gnu.wildebeest.org> (raw)
In-Reply-To: <877cpae033.fsf@gentoo.org>

Hi,

On Fri, Sep 01, 2023 at 10:02:23AM +0100, Sam James via Libc-alpha wrote:
> Florian Weimer via Libc-alpha <libc-alpha@sourceware.org> writes:
> > * 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.
> 
> Have we communicated that to the overseers though (that it's so serious
> it's worth moving services over)?
> Obviously there's https://sourceware.org/bugzilla/show_bug.cgi?id=29713
> already from you, but that's not the same as "this is a showstopper".
> 
> I wasn't aware this was a serious blocker given b2 helps collect the
> Reviewed-bys anyway. But I can understand it being a pain for some
> people's workflows.

Sorry this is being resolved slowly. But as you can see in the bug
progress is being made, we just upgraded our mailman instance again
last week. I had requested testers a couple of months ago [1], but
didn't get much/any response, so I thought this wasn't very urgent. I
think we are ready to switch the list to not use From rewriting for
lists that want that. We could test it next week?

Cheers,

Mark

[1] https://inbox.sourceware.org/libc-alpha/Y2GocuarFslwvb9j@wildebeest.org/

  reply	other threads:[~2023-09-01  9:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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             ` Mark Wielaard [this message]
2023-09-01 11:52               ` dmarc, dkim and From rewriting Florian Weimer
2023-09-01  9:03           ` [Action Required] glibc decision to use CTI services Andrew Pinski
2023-09-01 11:49             ` 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
2023-09-04  8:48 dmarc, dkim and From rewriting Mark Wielaard
2023-09-06 18:49 ` Mark Wielaard
2023-09-08 17:21   ` Mark Wielaard

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=20230901092133.GB22481@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).