From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by sourceware.org (Postfix) with ESMTPS id 09E3C385B833; Fri, 3 Apr 2020 15:58:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 09E3C385B833 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 8A01FABE9; Fri, 3 Apr 2020 15:58:51 +0000 (UTC) Subject: Re: mailman customization To: "Frank Ch. Eigler" Cc: Jakub Jelinek , Tobias Burnus , overseers@gcc.gnu.org, gcc mailing list , gfortran References: <3f4869fd-d852-a8a6-117f-e767a417ff95@codesourcery.com> <8d833f8d-243f-e8b8-69ed-124ef33b7746@codesourcery.com> <20200309102520.GQ2156@tucnak> <69bd8396-1e11-6b87-18f2-658fd171ebc2@suse.cz> <2b833ee3-ffdf-c002-a476-458465f0c6bd@suse.cz> <20200403155420.GI323051@elastic.org> From: =?UTF-8?Q?Martin_Li=c5=a1ka?= Message-ID: <57e8655b-f4f0-ebcc-8991-0f1f336296c3@suse.cz> Date: Fri, 3 Apr 2020 17:58:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200403155420.GI323051@elastic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-17.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, 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: Fri, 03 Apr 2020 15:58:54 -0000 On 4/3/20 5:54 PM, Frank Ch. Eigler wrote: > 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. That would be great. Should I create a git repo where we'll stack these changes? > 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#. Can you please do it for me as I don't have any experience with Fedora packaging? Thank you, Martin > > - FChE >