From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36748 invoked by alias); 11 Jul 2019 18:13:44 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 36738 invoked by uid 89); 11 Jul 2019 18:13:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy= X-Spam-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Message-ID: <38c77651b5696da99560f36d5285741ca9d1b514.camel@klomp.org> Subject: Re: [PATCH] Replace project contact email with bzip2-devel@sourceware.org. From: Mark Wielaard To: bzip2-devel@sourceware.org Cc: Julian Seward Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: <1562868211-28019-1-git-send-email-mark@klomp.org> References: <1562868211-28019-1-git-send-email-mark@klomp.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-SW-Source: 2019-q3/txt/msg00024.txt.bz2 On Thu, 2019-07-11 at 20:03 +0200, Mark Wielaard wrote: > @@ -829,7 +829,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) > " The user's manual, Section 4.3, has more info on (1) and (2).\= n" > " \n" > " If you suspect this is a bug in bzip2, or are unsure about (1)= \n" > - " or (2), feel free to report it to me at: jseward@acm.org.\n" > + " or (2), feel free to report it to: bzip2-devel@sourceware.org.= \n" > " Section 4.3 of the user's manual describes the info a useful\n" > " bug report should have. If the manual is available on your\n" > " system, please try and read it before mailing me. If you don'= t\n" > @@ -852,7 +852,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n ) > " The user's manual, Section 4.3, has more info on (2) and (3).\= n" > " \n" > " If you suspect this is a bug in bzip2, or are unsure about (2)= \n" > - " or (3), feel free to report it to me at: jseward@acm.org.\n" > + " or (3), feel free to report it to: bzip2-devel@sourceware.org.= \n" > " Section 4.3 of the user's manual describes the info a useful\n" > " bug report should have. If the manual is available on your\n" > " system, please try and read it before mailing me. If you don'= t\n" BTW. This SIGSEGV/BUS signal handler might be why we haven't seen more crashers when fuzzing bzip2 directly. That is another reason to introduce targeted fuzzer entry points. Cheers, Mark