From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: binutils@sourceware.org, Joel Brobecker <brobecker@adacore.com>,
Indu Bhagat <indu.bhagat@oracle.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [RFA] src-release.sh: Fix gdb source tarball build failure due to libsframe
Date: Mon, 28 Nov 2022 07:44:48 -0700 [thread overview]
Message-ID: <87o7srp28v.fsf@tromey.com> (raw)
In-Reply-To: <20221127125325.263577-1-brobecker@adacore.com> (Joel Brobecker via Gdb-patches's message of "Sun, 27 Nov 2022 16:53:25 +0400")
>>>>> "Joel" == Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:
Joel> ChangeLog:
Joel> * src-release.sh (GDB_SUPPORT_DIRS): Add libsframe.
Joel> Ok to apply to master?
Looks good to me.
I think we recently agreed that gdb and binutils maintainers can approve
patches like this... ?
thanks,
Tom
next prev parent reply other threads:[~2022-11-28 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 12:53 Joel Brobecker
2022-11-28 14:44 ` Tom Tromey [this message]
2022-11-30 3:37 ` Joel Brobecker
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=87o7srp28v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=indu.bhagat@oracle.com \
/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).