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