From: Simon Marchi <simark@simark.ca>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Jonathan Wakely <jwakely@redhat.com>
Cc: Richard Earnshaw <rearnsha@arm.com>,
gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] toplevel: unify the GCC and GDB/binutils .editorconfig files
Date: Wed, 1 Oct 2025 10:58:49 -0400 [thread overview]
Message-ID: <4dd1e712-38a2-49f4-ac5a-77ed54b58aa0@simark.ca> (raw)
In-Reply-To: <cca88c27-52a1-45bf-b6b6-3d5cc58adae9@arm.com>
On 10/1/25 10:44 AM, Richard Earnshaw (lists) wrote:
> On 24/09/2025 09:23, Jonathan Wakely wrote:
>> On Tue, 23 Sept 2025 at 18:11, Simon Marchi wrote:
>>>
>>> On 9/23/25 12:49 PM, Richard Earnshaw wrote:
>>>> Both GCC and GDB/binutils now have root editorconfig files. It would
>>>> make sense to unify them as this sets the general tone for these
>>>> projects.
>>>>
>>>> ChangeLog:
>>>> * .editorconfig: Unify the GCC and GDB/binutils root config.
>>>
>>> From the point of view of GDB, this looks fine, thanks for doing this.
>>
>>
>> This looks like a vast improvement on the bare-bones config I added
>> for GCC, thanks.
>>
>
> I've now pushed this to the GCC repo, but I've not yet heard anything from the binutils maintainers. Do I need to wait for them, or is Simon's ack for GDB enough?
>
> R.
I think you can go ahead and push it, I really don't see how it could be
controversial.
Simon
next prev parent reply other threads:[~2025-10-01 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 16:49 [PATCH 0/1] Unify the GCC and GDB/Binutils " Richard Earnshaw
2025-09-23 16:49 ` [PATCH 1/1] toplevel: unify the GCC and GDB/binutils " Richard Earnshaw
2025-09-23 17:03 ` Simon Marchi
2025-09-24 8:23 ` Jonathan Wakely
2025-10-01 14:44 ` Richard Earnshaw (lists)
2025-10-01 14:58 ` Simon Marchi [this message]
2025-10-01 15:22 ` Richard Earnshaw (lists)
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=4dd1e712-38a2-49f4-ac5a-77ed54b58aa0@simark.ca \
--to=simark@simark.ca \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jwakely@redhat.com \
--cc=rearnsha@arm.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