commit ef2b9c7e8b495c7e070657d6777b20b7ed63aa5c
Author: Raf Czlonka <[email protected]>
Date: Tue Mar 6 03:29:25 2018 +0000
Use "mailing list(s)" consistently.
diff --git a/suckless.org/community.md b/suckless.org/community.md
index ba77ec3f..29407845 100644
--- a/suckless.org/community.md
+++ b/suckless.org/community.md
@@ -11,8 +11,8 @@ Mailing lists
### Best practice
-When beginning a new discussion on the mailinglists, except for the wiki@
-mailinglist, prepend your subject with the project name you are referring to.
+When beginning a new discussion on the mailing lists, except for the wiki@
+mailing list, prepend your subject with the project name you are referring to.
This makes it easier for project maintainers to answer your questions.
@@ -58,13 +58,13 @@ When sending a patch use the following commands:
git send-email --subject-prefix="$(basename $(pwd))][PATCH" \
--to [email protected] -1
-This will send the last commit of the repository to the mailinglist adding a
+This will send the last commit of the repository to the mailing list adding a
prefix to the subject which includes the appropriate project name. This allows
easier referencing and filtering of the e-mails for the maintainers subscribed
to hackers@.
Be sure to have setup your sender address in git and be subscribed to the
-mailinglist so you can see eventual comments on your patches.
+mailing list so you can see eventual comments on your patches.
* `hackers+subscribe@MAILHOST` - subscribe to the mailing list (read/write)
* `hackers+subscribe-digest@MAILHOST` - subscribe to the digest version of the
mailing list (read/write)
