doc: Mention upgrades that trigger a lot of rebuilds.

* HACKING (Commit Access): Mention upgrades that trigger a lot rebuilds.

1 files changed, 2 insertions, 1 deletions

diff --git a/HACKING b/HACKING
index 6600397554..9e47b9703b 100644
--- a/HACKING
+++ b/HACKING
@@ -159,7 +159,8 @@ 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,
 and have done a reasonable copyright and license auditing.)  Likewise for
-package upgrades.  We have a mailing list for commit notifications
+package upgrades, except upgrades that trigger a lot of rebuilds (for example,
+upgrading GnuTLS or GLib.)  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’.