diff options
| author | Pierre-Antoine Rault <par@rigelk.eu> | 2014-03-09 17:10:27 +0100 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2014-03-10 23:43:31 +0100 |
| commit | 5ff3c4b8207eb2fbbc48c9f429ccb65690def5ee (patch) | |
| tree | c7a540ad358d8efd0d56e859cbd8ec32bfbfff01 /HACKING | |
| parent | 8a1f6a7e02afbe63dfa1193282c8b6807b845db2 (diff) | |
| download | guix-5ff3c4b8207eb2fbbc48c9f429ccb65690def5ee.tar.gz | |
doc: Update packaging guidelines.
* HACKING (Submitting Patches): Mention 'git send-mail'. * doc/guix.texi (Packaging Guidelines): More details on how to prepare a package module. (Contributing): Add reference to #guix channel on Freenode. Co-authored-by: Ludovic Courtès <ludo@gnu.org>
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/HACKING b/HACKING index 0dc2908318..6600397554 100644 --- a/HACKING +++ b/HACKING @@ -2,8 +2,9 @@ #+TITLE: Hacking GNU Guix and Its Incredible Distro -Copyright © 2012, 2013 Ludovic Courtès <ludo@gnu.org> +Copyright © 2012, 2013, 2014 Ludovic Courtès <ludo@gnu.org> Copyright © 2013 Nikita Karetnikov <nikita@karetnikov.org> +Copyright © 2014 Pierre-Antoine Rault <par@rigelk.eu> Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright @@ -85,7 +86,11 @@ wrapping it, swallowing or rejecting the following s-expression, etc. Development is done using the Git distributed version control system. Thus, access to the repository is not strictly necessary. We welcome contributions in the form of patches as produced by ‘git format-patch’ sent to -guix-devel@gnu.org. Please write commit logs in the [[http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs][GNU ChangeLog format]]. +guix-devel@gnu.org. Please write commit logs in the [[http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs][GNU ChangeLog +format]]; you can check the commit history for examples. + +When posting a patch to the mailing list, use "[PATCH] ..." as a subject. You +may use your email client or the ‘git send-mail’ command. As you become a regular contributor, you may find it convenient to have write access to the repository (see below.) |