commit d095906810338620792ac67458496d7439036161 parent 1c1cee8568cd9521cac30fc3669a61b6d4d341ed Author: Christoph Lohmann <20h@r-36.net> Date: Wed, 6 Jan 2016 15:39:18 +0100 Move the patch hints to the appropriate mailinglist. Diffstat:
| M | dwm.suckless.org/patches/index.md | | | 6 | ------ |
| M | suckless.org/community.md | | | 14 | ++++++++++++++ |
2 files changed, 14 insertions(+), 6 deletions(-)
diff --git 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 @@ -37,6 +37,20 @@ following addresses to perform the described action. ### `hackers@suckless.org` +When sending a patch use the following commands: + + cd $project + git send-email --subject-prefix="$(basename $(pwd))][PATCH" \ + --to hackers@suckless.org -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)