From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "H.J. Lu via Binutils" <binutils@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>,
GDB <gdb-patches@sourceware.org>,
Fangrui Song <maskray@google.com>
Subject: Re: [gdb-11-branch: Patch 0/3] Support SHT_RELR (.relr.dyn) section
Date: Sun, 16 Jan 2022 05:30:41 -0800 [thread overview]
Message-ID: <CAMe9rOoOKw9v-=VOtj7EGxwcVM1QQP08EsgRBBh8-U5HC5DaeQ@mail.gmail.com> (raw)
In-Reply-To: <YePxj1eyY2A/v5mS@adacore.com>
On Sun, Jan 16, 2022 at 2:21 AM Joel Brobecker <brobecker@adacore.com> wrote:
>
> > 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?
>
It is a dup of
https://sourceware.org/bugzilla/show_bug.cgi?id=28758
--
H.J.
prev parent reply other threads:[~2022-01-16 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 17:45 H.J. Lu
2022-01-09 17:45 ` [gdb-11-branch: Patch 1/3] readelf: Support RELR in -S and -d and output H.J. Lu
2022-01-09 17:45 ` [gdb-11-branch: Patch 2/3] readelf: Support SHT_RELR/DT_RELR for -r H.J. Lu
2022-01-09 17:45 ` [gdb-11-branch: Patch 3/3] bfd_section_from_shdr: Support SHT_RELR sections H.J. Lu
2022-01-10 2:44 ` [gdb-11-branch: Patch 0/3] Support SHT_RELR (.relr.dyn) section Simon Marchi
2022-01-10 13:03 ` H.J. Lu
2022-01-16 9:44 ` Joel Brobecker
2022-01-16 10:21 ` Joel Brobecker
2022-01-16 13:30 ` H.J. Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOoOKw9v-=VOtj7EGxwcVM1QQP08EsgRBBh8-U5HC5DaeQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=maskray@google.com \
--cc=simon.marchi@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).