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 | |
| parent | 0a56fadb60d703a12316febdf277471b9931bb05 (diff) | |
doc: Mention copyright/license auditing in `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 patches include fixing typos, etc.) For patches that just add a new package, and a simple one, it’s OK to commit, -if you’re confident (which means you successfully built it in a chroot setup.) -Likewise for package upgrades. We have a mailing list for commit -notifications (guix-commits@gnu.org), so people can notice. Before pushing -your changes, make sure to run ‘git pull --rebase’. +if you’re confident (which means you successfully built it in a chroot setup, +and have done a reasonable copyright and license auditing.) Likewise for +package upgrades. We have a mailing list for commit notifications +(guix-commits@gnu.org), so people can notice. Before pushing your changes, +make sure to run ‘git pull --rebase’. For anything else, please post to bug-guix@gnu.org and leave time for a review, without committing anything. If you didn’t receive any reply |