Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
	gdb-patches@sourceware.org
Cc: jwakely@redhat.com, Richard Earnshaw <rearnsha@arm.com>
Subject: [PATCH 0/1] Unify the GCC and GDB/Binutils .editorconfig files
Date: Tue, 23 Sep 2025 17:49:58 +0100	[thread overview]
Message-ID: <20250923164959.565000-1-rearnsha@arm.com> (raw)

Both GCC and the GDB/binutils projects have a top-level .editorconfig file.  Like much
of the toplevel configury it would seem sensible to try to keep this unified.  This patch
is an initial stab at doing that.

I've also added considerably more than was in either current file in an attempt to
handle some of GCC's supported languages and the test/build systems.  I've had to
make educated guesses for some of these languages based on a small sample of the
existing code bases.  If I've got them wrong please let me know.

The diff is technically against the current GCC .editorconfig, but in truth there's
not much that isn't changed in the patch, so I think it should be understandable
by everyone.

Comments welcome.

R.

Richard Earnshaw (1):
  toplevel: unify the GCC and GDB/binutils .editorconfig files

 .editorconfig | 122 ++++++++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 113 insertions(+), 9 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-09-23 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 16:49 Richard Earnshaw [this message]
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
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=20250923164959.565000-1-rearnsha@arm.com \
    --to=rearnsha@arm.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jwakely@redhat.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