From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) by sourceware.org (Postfix) with ESMTPS id 283DD3858D35 for ; Sun, 16 Jan 2022 10:21:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 283DD3858D35 Received: by mail-wm1-x334.google.com with SMTP id c2so8923533wml.1 for ; Sun, 16 Jan 2022 02:21:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=prqxghwEV5jClGgYpG8PSrM+9gZ/VMlt4nlfPM0fMds=; b=xLSmbVKRPmxVbx9jbelZjDO6TTnPW6tU3SFqc72brv5CNRJEzf5eW4qI1iLyr8nxwr gb9y0xIGEzcdxvHR5LEay16LT3oCiNbcfLoNNUwrYGG4CyP8iABbFVejfq/O87IHfL3N 1Kn+LJVDjLqgZ/NrkJTngkulnnQ2T692BUyQrHYhLg3lhjdskOvzmAD6TWLM5ZQHIZrt G17/d5m9e7RZdjC8EDU7z7MPq4v4gpPJWDpMIeLPZy2cSC4VZJPhGc+MioQ26pzSUr2b uTf96BWfwspAo0PcAfn0uLMCFUWUhunG1Z64Xm8e2MvVmJFWCfQgAyFRMwb33qlUezLR 3JiQ== X-Gm-Message-State: AOAM533/NCPQ2bP6jj2TbSrhS2cQ4WNV13r85LqvxEJR55B/QXNxmt7X SPM5CKD725Omwzvo68M4jMwdqNtlCz39 X-Google-Smtp-Source: ABdhPJwAlVy5jfgDjG4REF9kCjq6WZh6F2m4tvm0Uf2R5/04hHg+n6qgkjrZ8JKBGflr8MdGQDAsBQ== X-Received: by 2002:a05:6000:2ac:: with SMTP id l12mr5267592wry.165.1642328467307; Sun, 16 Jan 2022 02:21:07 -0800 (PST) Received: from takamaka.home (lfbn-reu-1-503-119.w92-130.abo.wanadoo.fr. [92.130.90.119]) by smtp.gmail.com with ESMTPSA id i12sm7894739wrf.100.2022.01.16.02.21.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 16 Jan 2022 02:21:06 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id DDF65A84C2; Sun, 16 Jan 2022 14:21:03 +0400 (+04) Date: Sun, 16 Jan 2022 14:21:03 +0400 From: Joel Brobecker To: "H.J. Lu via Binutils" , "H.J. Lu" Cc: Simon Marchi , GDB , Fangrui Song , Joel Brobecker Subject: Re: [gdb-11-branch: Patch 0/3] Support SHT_RELR (.relr.dyn) section Message-ID: References: <20220109174504.1120244-1-hjl.tools@gmail.com> <5c2a1e87-b732-7d1d-f3c5-cf5b4cefa430@polymtl.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=unavailable autolearn_force=no version=3.4.4 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: Sun, 16 Jan 2022 10:21:09 -0000 > Just a heads up that, to backport changes to a GDB branch after > the first release was done, we should create a GDB/PR and set > the target milestone to the corresponding release. Otherwise, > the announcement is going to miss the fact that this change > was included in the release. > > If you see my email as I'm sending it, can you take care of this > right away? Otherwise, I'll create one, but I cannot be as informative > as you might be, and that's one of the main point of having those PRs. I am about to start working on making the GDB 11.2 release, so I've created the following PR, to have it ready: https://sourceware.org/bugzilla/show_bug.cgi?id=28785 Something that also became more obvious to me as I created the PR and would have been useful in assessing whether or not we should backport the patches is an explanation of why we should be backporting them. The commits make it sound like they are about fixing readelf and objcopy, which makes me wonder why you proposed them for a GDB release. Can you update the PR so as to provide more information there, please? -- Joel