From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21]) by sourceware.org (Postfix) with ESMTPS id 2037E38930E8; Wed, 29 Apr 2020 10:13:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2037E38930E8 Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1jTjiq-0000UD-Rk; Wed, 29 Apr 2020 10:13:44 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1jTjiq-0006hs-Ow; Wed, 29 Apr 2020 12:13:44 +0200 From: Florian Weimer To: "Frank Ch. Eigler" Cc: Overseers mailing list , libc-alpha@sourceware.org Subject: Re: Early blind copy for libc-alpha References: <87y2qeejd2.fsf@mid.deneb.enyo.de> <20200429100414.GD21677@redhat.com> Date: Wed, 29 Apr 2020 12:13:44 +0200 In-Reply-To: <20200429100414.GD21677@redhat.com> (Frank Ch. Eigler's message of "Wed, 29 Apr 2020 06:04:14 -0400") Message-ID: <877dxyeh0n.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-8.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2020 10:13:53 -0000 * Frank Ch. Eigler: >> Would it be possible to get an early copy of messages sent to >> before they go into Mailman? > > The closest thing I can think of is adding a new alias, like > libc-alpha-raw, which expands to libc-alpha and you? Thanks. No, that's not really useful, sorry. >> It will help those of us who apply patches on other people's behalf, >> without having to undo the Mailman mangling first. > > Please also see alternatives outlined in: > https://sourceware.org/pipermail/overseers/2020q1/016783.html I guess moving glibc development to a platform that does not have this problem is something we have to consider at this point. I do not think adding even more requirements for contributors is the appropriate way forward.