diff options
| author | Ludovic Courtès <ludo@gnu.org> | 2013-06-10 00:00:33 +0200 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2013-06-10 00:00:33 +0200 |
| commit | e20ec9cc5165f1312bd1a057bf4da48bb5102385 (patch) | |
| tree | adc39175f8e2e2a1aa9935eef620fe8e6119f78f /HACKING | |
| parent | 0a56fadb60d703a12316febdf277471b9931bb05 (diff) | |
doc: Mention copyright/license auditing in `HACKING'.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 9 |
1 files changed, 5 insertions, 4 deletions
| @@ -115,10 +115,11 @@ Non-trivial patches should always be posted to bug-guix@gnu.org (trivial | |||
| 115 | patches include fixing typos, etc.) | 115 | patches include fixing typos, etc.) |
| 116 | 116 | ||
| 117 | For patches that just add a new package, and a simple one, it’s OK to commit, | 117 | For patches that just add a new package, and a simple one, it’s OK to commit, |
| 118 | if you’re confident (which means you successfully built it in a chroot setup.) | 118 | if you’re confident (which means you successfully built it in a chroot setup, |
| 119 | Likewise for package upgrades. We have a mailing list for commit | 119 | and have done a reasonable copyright and license auditing.) Likewise for |
| 120 | notifications (guix-commits@gnu.org), so people can notice. Before pushing | 120 | package upgrades. We have a mailing list for commit notifications |
| 121 | your changes, make sure to run ‘git pull --rebase’. | 121 | (guix-commits@gnu.org), so people can notice. Before pushing your changes, |
| 122 | make sure to run ‘git pull --rebase’. | ||
| 122 | 123 | ||
| 123 | For anything else, please post to bug-guix@gnu.org and leave time for a | 124 | For anything else, please post to bug-guix@gnu.org and leave time for a |
| 124 | review, without committing anything. If you didn’t receive any reply | 125 | review, without committing anything. If you didn’t receive any reply |
