From d0c64188b68cceb93e6a61eba123dac5e47e2c0f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= <ludo@gnu.org>
Date: Sun, 11 May 2014 12:11:09 +0200
Subject: [PATCH] doc: Mention upgrades that trigger a lot of rebuilds.

* HACKING (Commit Access): Mention upgrades that trigger a lot rebuilds.
---
 HACKING | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/HACKING b/HACKING
index 66003975544..9e47b9703b0 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’.
 
-- 
GitLab