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 0B2273858002 for ; Thu, 7 Apr 2022 16:12:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0B2273858002 Received: from fencepost.gnu.org ([2001:470:142:3::e]:51322) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ncUjo-0003Cd-19; Thu, 07 Apr 2022 12:12:00 -0400 Received: from [87.69.77.57] (port=2753 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ncUjn-0005nB-EO; Thu, 07 Apr 2022 12:11:59 -0400 Date: Thu, 07 Apr 2022 19:12:08 +0300 Message-Id: <83pmlsc1pj.fsf@gnu.org> From: Eli Zaretskii To: Tom Tromey Cc: gdb-patches@sourceware.org, brobecker@adacore.com In-Reply-To: <87ee28anbg.fsf@tromey.com> (message from Tom Tromey on Thu, 07 Apr 2022 10:08:19 -0600) Subject: Re: GDB 12.0.90 available for testing References: <20220320055815.2A90FA4D6C@takamaka.home> <83v8w0ag5j.fsf@gnu.org> <83tubkadx4.fsf@gnu.org> <87ee28anbg.fsf@tromey.com> X-Spam-Status: No, score=2.0 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Thu, 07 Apr 2022 16:12:02 -0000 > From: Tom Tromey > Cc: Joel Brobecker , Eli Zaretskii > Date: Thu, 07 Apr 2022 10:08:19 -0600 > > >> My understanding is that gnulib updates in GDB are performed only > >> as needed, by the people who need it. > > Eli> Fine with me, thanks. > > If there's a particular gnulib import that's needed, I'm happy to do it. > I'd just need to know the revision. It isn't a single update. I identified at least 2, maybe 3 changes Gnulib installed based on my reports of problems found in GDB 11. > Or, maybe we should just adopt a policy of doing an import from > gnulib HEAD on trunk after a release branch is made? IMO, it would be best. But that's not my call, especially since Joel says there seems to be a policy about that. > I'm not sure whether we want to attempt an update on the GDB 12 branch. No, I don't think we should. It's too late for GDB 12, IMO.