From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: 58443@debbugs.gnu.org
Cc: "\(" <paren@disroot.org>
Subject: [bug#58443] [PATCH 0/1] Add EditorConfig specification.
Date: Tue, 11 Oct 2022 16:12:57 +0100 [thread overview]
Message-ID: <20221011151257.24989-1-paren@disroot.org> (raw)
This patch adds a .editorconfig file to the project root. This is especially
useful for ~~nonbelievers~~ non-Emacs users.
( (1):
Add EditorConfig specification.
.editorconfig | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 .editorconfig
--
2.38.0
next reply other threads:[~2022-10-11 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 15:12 ( via Guix-patches via [this message]
2022-10-11 15:33 ` bug#58443: Close duplicate ( via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221011151257.24989-1-paren@disroot.org \
--to=guix-patches@gnu.org \
--cc=58443@debbugs.gnu.org \
--cc=paren@disroot.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).