From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6458 invoked by alias); 24 Dec 2019 15:30:48 -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 6406 invoked by uid 89); 24 Dec 2019 15:30:44 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=U*gdb-patches, gdb-patches@sourceware.org, gdbpatchessourcewareorg, receipt X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 24 Dec 2019 15:30:42 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:45274) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ijm8v-0002D8-9D; Tue, 24 Dec 2019 10:30:41 -0500 Received: from [176.228.60.248] (port=4247 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ijm8u-0001Qo-AM; Tue, 24 Dec 2019 10:30:40 -0500 Date: Tue, 24 Dec 2019 15:30:00 -0000 Message-Id: <83h81pwxkb.fsf@gnu.org> From: Eli Zaretskii To: Joel Brobecker CC: cbiesinger@google.com, gdb-patches@sourceware.org In-reply-to: <20191224035315.GC25918@adacore.com> (message from Joel Brobecker on Tue, 24 Dec 2019 07:53:15 +0400) Subject: Re: GDB 9.0.90 available for testing 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> <20191224035315.GC25918@adacore.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00997.txt.bz2 > Date: Tue, 24 Dec 2019 07:53:15 +0400 > From: Joel Brobecker > Cc: cbiesinger@google.com, gdb-patches@sourceware.org > > > > - 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. OK, thanks. I will try to keep an eye on Readline.