commit d095906810338620792ac67458496d7439036161
Author: Christoph Lohmann <[email protected]>
Date: Wed Jan 6 15:39:18 2016 +0100
Move the patch hints to the appropriate mailinglist.
diff --git a/dwm.suckless.org/patches/index.md
b/dwm.suckless.org/patches/index.md
index 1ce5e74..4b95149 100644
--- a/dwm.suckless.org/patches/index.md
+++ b/dwm.suckless.org/patches/index.md
@@ -13,14 +13,8 @@ For tarballs:
cd modified-dwm-directory/..
diff -up original-dwm-directory modified-dwm-directory >
dwm-X.Y-yourpatchname.diff
-To send the last commit to the mailing lists (@hackers):
-
- cd dwm-directory
- git send-email --subject-prefix="$(basename $PWD)][PATCH" -1
-
where `X.Y` is a dwm tag name or version number.
-
patch application
-----------------
For git users, use `-3` to fix the conflict easily:
diff --git a/suckless.org/community.md b/suckless.org/community.md
index 61cac06..4108fad 100644
--- a/suckless.org/community.md
+++ b/suckless.org/community.md
@@ -37,6 +37,20 @@ following addresses to perform the described action.
### `[email protected]`
+When sending a patch use the following commands:
+
+ cd $project
+ 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
+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.
+
* `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)
* `hackers+subscribe-nomail@MAILHOST` - subscribe without receiving e-mails
from the mailing list (write)
