From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 2A0EF3858C5F; Sat, 30 Sep 2023 20:44:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2A0EF3858C5F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: by gnu.wildebeest.org (Postfix, from userid 1000) id 1764E302FDCD; Sat, 30 Sep 2023 22:44:33 +0200 (CEST) Date: Sat, 30 Sep 2023 22:44:33 +0200 From: Mark Wielaard To: gcc-patches , libstdc++@gcc.gnu.org, jit@gcc.gnu.org, gcc-rust@gcc.gnu.org Cc: jeffreyalaw@gmail.com, philip.herron@embecosm.com, herron.philip@googlemail.com, jason@redhat.com, dmalcolm@redhat.com, toon@moene.org, jwakely.gcc@gmail.com Subject: Re: gcc-patches From rewriting mailman settings Message-ID: <20230930204433.GA32765@gnu.wildebeest.org> References: <451593065.12041.1694473092764@jenkins.jenkins> <1d08987cbf153edb72728ba2af4918f240a119e9.camel@klomp.org> <20230917200437.GC6719@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230917200437.GC6719@gnu.wildebeest.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-3028.7 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, On Sun, Sep 17, 2023 at 10:04:37PM +0200, Mark Wielaard wrote: > On Tue, Sep 12, 2023 at 05:00:07PM +0200, Mark Wielaard wrote: > > We (Jeff or anyone else with mailman admin privs) could use the same > > settings for gcc-patches. The settings that need to be set are in that > > bug: > > > > - subject_prefix (general): (empty) > > - from_is_list (general): No > > - anonymous_list (general): No > > - first_strip_reply_to (general): No > > - reply_goes_to_list (general): Poster > > - reply_to_address (general): (empty) > > - include_sender_header (general): No > > - drop_cc (general): No > > - msg_header (nondigest): (empty) > > - msg_footer (nondigest): (empty) > > - scrub_nondigest (nondigest): No > > - dmarc_moderation_action (privacy): Accept > > - filter_content (contentfilter): No > > > > The only visible change (apart from no more From rewriting) is that > > HTML multi-parts aren't scrubbed anymore (that would be a message > > altering issue). The html part is still scrubbed from the > > inbox.sourceware.org archive, so b4 works just fine. But I don't know > > what patchwork.sourceware.org does with HTML attachements. Of course > > people really shouldn't sent HTML attachments to gcc-patches, so maybe > > this is no real problem. > > Although there were some positive responses (on list and on irc) it is > sometimes hard to know if there really is consensus for these kind of > infrastructure tweaks. But I believe there is at least no sustained > opposition to changing the gcc-patches mailman setting as proposed > above. > > So unless someone objects I like to make this change Tuesday September > 19 around 08:00 UTC. > > And if there are no complaints at Cauldron we could do the same for > the other patch lists the week after. Since there were no complaints (and some happy users) and we didn't real issues (there was an issue when using the Errors-To header, which might break your dkim signature, but the only user of Errors-To has dropped it) the jit, libstdc++, fortran and gcc-rust lists now also have the above mailman settings. The admin email address for fortran was updated to Toon's new address and the one for libstdc++ was changed from bkoz to jwakely. If there are any issues with the list settings please discuss on the overseers@sourceware.org mailinglist. Cheers, Mark > > > [1] https://patchwork.sourceware.org/project/gcc/list/ > > > [2] https://sourceware.org/bugzilla/show_bug.cgi?id=29713