From: Hong Xu <hong@topbug.net>
To: zsh-workers@zsh.org
Subject: [PATCH] Update .editorconfig file: comment lines should occupy individual lines
Date: Sat, 08 Jun 2013 00:32:43 -0700 [thread overview]
Message-ID: <51B2DE1B.4090701@topbug.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
Hi All,
The attachment fixes an issue of the .editorconfig file in the zsh
repository: comments should occupy individual lines, but not be appended
to another line.
Thanks,
Hong
[-- Attachment #2: editorconfig.patch --]
[-- Type: text/plain, Size: 242 bytes --]
diff --git a/.editorconfig b/.editorconfig
index 58421c0..145dc37 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -1,4 +1,6 @@
-root = true # Top-most editorconfig file
+# Top-most editorconfig file
+
+root = true
[*]
end_of_line = lf
next reply other threads:[~2013-06-08 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 7:32 Hong Xu [this message]
2013-06-08 18:45 ` Aaron Schrab
2013-06-08 18:52 ` Hong Xu
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=51B2DE1B.4090701@topbug.net \
--to=hong@topbug.net \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).