From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Luis Machado <luis.machado@arm.com>,
gdb-patches@sourceware.org,
"binutils@sourceware.org" <binutils@sourceware.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix disabling of year 2038 support on 32-bit hosts by default
Date: Tue, 06 Feb 2024 17:57:46 -0300 [thread overview]
Message-ID: <87o7ctxqd1.fsf@linaro.org> (raw)
In-Reply-To: <CA+=Sn1nv5zxaUO4e1NY7VWShtbhg3=YouCL3-tcm9qv5Jyk_Sw@mail.gmail.com>
Hello Andrew,
Andrew Pinski <pinskia@gmail.com> writes:
> On Mon, Feb 5, 2024 at 10:40 AM Thiago Jung Bauermann
> <thiago.bauermann@linaro.org> wrote:
>>
>>
>> Thiago Jung Bauermann <thiago.bauermann@linaro.org> writes:
>>
>> > Hello Luis,
>> >
>> > Luis Machado <luis.machado@arm.com> writes:
>> >>
>> >> Approved-By: Luis Machado <luis.machado@arm.com>
>> >
>> > Thanks! Since this is a patch for the repository top-level, is your
>> > approval sufficient to commit the patch, or should I have approval from
>> > a binutils maintainer as well?
>>
>> Answering my own question: binutils/MAINTAINERS says:
>>
>> GDB global maintainers also have permission to commit and approve
>> patches to the top level files and to those parts of bfd files
>> primarily used by GDB.
>>
>> So pushed as commit 9c0aa4c53104.
>
> Please also submit/commit to the gcc trunk too since the toplevel
> configure should be insync between the 2 repos.
I don't have commit access to the gcc repo so I sent a patch to the
gcc-patches mailing list.
--
Thiago
prev parent reply other threads:[~2024-02-06 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240203031408.137939-1-thiago.bauermann@linaro.org>
2024-02-03 16:39 ` Thiago Jung Bauermann
2024-02-06 8:26 ` Mark Wielaard
2024-02-05 14:59 ` Luis Machado
2024-02-05 17:25 ` Thiago Jung Bauermann
2024-02-05 18:39 ` Thiago Jung Bauermann
2024-02-05 18:57 ` Andrew Pinski
2024-02-06 20:57 ` Thiago Jung Bauermann [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=87o7ctxqd1.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=pinskia@gmail.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).