From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 3305C385782C for ; Sun, 20 Sep 2020 06:09:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3305C385782C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=eliz@gnu.org Received: from fencepost.gnu.org ([2001:470:142:3::e]:59224) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJsXc-0007Pu-Vs; Sun, 20 Sep 2020 02:09:40 -0400 Received: from [176.228.60.248] (port=4237 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kJsXc-0003k0-Ag; Sun, 20 Sep 2020 02:09:40 -0400 Date: Sun, 20 Sep 2020 09:09:39 +0300 Message-Id: <83ft7d0yjg.fsf@gnu.org> From: Eli Zaretskii To: Simon Marchi Cc: brobecker@adacore.com, gdb-patches@sourceware.org In-Reply-To: <72a2558b-bcad-ecd9-7311-b3ef799ccfd8@simark.ca> (message from Simon Marchi on Sat, 19 Sep 2020 21:03:41 -0400) Subject: Re: GDB 10.1 release -- 2020-09-18 Update References: <20200918234602.GA4674@adacore.com> <72a2558b-bcad-ecd9-7311-b3ef799ccfd8@simark.ca> X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, 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: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2020 06:09:43 -0000 > From: Simon Marchi > Date: Sat, 19 Sep 2020 21:03:41 -0400 > > I just filed this ("TUI focus behavior change"), if it's considered a > bug then I think it should be put on the list of blockers. > > https://sourceware.org/bugzilla/show_bug.cgi?id=26638 Thanks, I think we should indeed try to fix this before the release.