From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu via Binutils" <binutils@sourceware.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
GDB <gdb-patches@sourceware.org>,
Fangrui Song <maskray@google.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [gdb-11-branch: Patch 0/3] Support SHT_RELR (.relr.dyn) section
Date: Sun, 16 Jan 2022 13:44:41 +0400 [thread overview]
Message-ID: <YePpCYapvWybSQ+C@adacore.com> (raw)
In-Reply-To: <CAMe9rOq0zP37mkfbqx38nqwfB4xKOZZEyaVgLqwoopB+zOVOnA@mail.gmail.com>
> > > Backport the following patches to add SHT_RELR (.relr.dyn) section support
> > > to gdb-11-branch.
> > >
> > > OK for gdb-11-branch?
[...]
> I am checking them in.
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.
--
Joel
next prev parent reply other threads:[~2022-01-16 9:44 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 [this message]
2022-01-16 10:21 ` Joel Brobecker
2022-01-16 13:30 ` H.J. Lu
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=YePpCYapvWybSQ+C@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--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).