From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31761 invoked by alias); 24 Dec 2019 03:53:22 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 31753 invoked by uid 89); 24 Dec 2019 03:53:22 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=upgrade, facing, receipt, him X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 24 Dec 2019 03:53:21 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 02338116602; Mon, 23 Dec 2019 22:53:20 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id sHpVs7onlJ1U; Mon, 23 Dec 2019 22:53:19 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 8C24A1165A4; Mon, 23 Dec 2019 22:53:19 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 4A721899C3; Tue, 24 Dec 2019 07:53:15 +0400 (+04) Date: Tue, 24 Dec 2019 03:53:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: cbiesinger@google.com, gdb-patches@sourceware.org Subject: Re: GDB 9.0.90 available for testing Message-ID: <20191224035315.GC25918@adacore.com> References: <20191211214745.E1CF0838D4@joel.gnat.com> <83tv604239.fsf@gnu.org> <835zic2wer.fsf@gnu.org> <83h81w14z1.fsf@gnu.org> <20191223074346.GC11677@adacore.com> <83tv5rvtgo.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83tv5rvtgo.fsf@gnu.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2019-12/txt/msg00991.txt.bz2 > > - Patch locally, and submit the patch to readline; > > This part is now done. Excellent, thank you. > > - Keep track of the patch submission on the readline end; > > How does one do that? I looked at the Readline's Git repository, but > couldn't find the patch there, and didn't understand the branch > arrangement. Perhaps Chet didn't yet push the changes? Or am I > missing something? That one is a little tougher. When I read Chet's message, I thought it was a little ambiguous, but the way I read it was that he was only acknowledging the receipt of the report and patch, so he hadn't had a chance to review and apply it. What I would do is ask him if he could let us know when it is reviewed and (hopefully) applied. If he forgets, that's not a huge deal, but we basically expose ourselves to facing that same issue again at the next readline upgrade. We could be even more proactive, but I don't think it would be worth the effort. -- Joel