From: Jonathan Wakely <jwakely@redhat.com>
To: gcc Mailing List <gcc@gcc.gnu.org>
Cc: Nick Clifton <nickc@redhat.com>
Subject: Editorconfig
Date: Mon, 16 Sep 2024 10:26:27 +0100 [thread overview]
Message-ID: <CACb0b4=uX+P4Wc5VtJGTrh=yMH+OMz9vnXuU5LAVRkz3-ZZzmw@mail.gmail.com> (raw)
I've pushed .editorconfig files for the libstdc++-v3 sub-directory:
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663071.html
As mentioned there, I'll experiment with similar files for the rest of
the tree. I will share those files and it would be helpful if people
who work on the rest of the tree could test them, because most of what
I do is isolated to the libstdc++-v3 dir!
reply other threads:[~2024-09-16 9:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACb0b4=uX+P4Wc5VtJGTrh=yMH+OMz9vnXuU5LAVRkz3-ZZzmw@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).