From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fche@elastic.org>
Received: from elastic.org (unknown [IPv6:2600:3c03::f03c:91ff:fe50:73f])
 by sourceware.org (Postfix) with ESMTPS id B6EA8385B833;
 Fri,  3 Apr 2020 15:54:25 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B6EA8385B833
Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org)
 by elastic.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
 (Exim 4.92.3) (envelope-from <fche@elastic.org>)
 id 1jKOeC-00039h-D4; Fri, 03 Apr 2020 15:54:20 +0000
Received: from very.elastic.org ([192.168.1.1])
 by elastic.org with esmtp (Exim 4.92.3)
 (envelope-from <fche@elastic.org>)
 id 1jKOeC-000XIs-2f; Fri, 03 Apr 2020 11:54:20 -0400
Received: from fche by very.elastic.org with local (Exim 4.92.3)
 (envelope-from <fche@very.elastic.org>)
 id 1jKOeC-002i47-20; Fri, 03 Apr 2020 11:54:20 -0400
Date: Fri, 3 Apr 2020 11:54:20 -0400
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Martin =?utf-8?B?TGnFoWth?= <mliska@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
 Tobias Burnus <tobias@codesourcery.com>, overseers@gcc.gnu.org,
 gcc mailing list <gcc@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: mailman customization
Message-ID: <20200403155420.GI323051@elastic.org>
References: <3f4869fd-d852-a8a6-117f-e767a417ff95@codesourcery.com>
 <AE4A7165-A17C-4341-99E4-C402B3647C71@tkoenig.net>
 <8d833f8d-243f-e8b8-69ed-124ef33b7746@codesourcery.com>
 <20200309102520.GQ2156@tucnak>
 <69bd8396-1e11-6b87-18f2-658fd171ebc2@suse.cz>
 <2b833ee3-ffdf-c002-a476-458465f0c6bd@suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2b833ee3-ffdf-c002-a476-458465f0c6bd@suse.cz>
X-Sender-Verification: ""
X-Sender-Verification: ""
X-Spam-Status: No, score=-106.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP,
 USER_IN_WHITELIST 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 <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 15:54:26 -0000

Hi -

> I believe we can quite easily customize mailman 2.1 to match our needs.
> The biggest challenge I see is a proper testing as I don't see it easy
> to set up a local mailman instance. I've got a patch that changes:

I suppose we can do some local RPM respins - as long as these changes
are small and rare.  Even with a deadish upstream, distro reporting
would be nice, at least at the centos/fedora point (?), as a reference
place to stash the patch and get us a bug#.

- FChE