me
/
guix
Archived
1
0
Fork 0
Code

doc: Mention upgrades that trigger a lot of rebuilds. 

* HACKING (Commit Access): Mention upgrades that trigger a lot rebuilds.
master
Ludovic Courtès 2014-05-11 12:11:09 +02:00
parent af8a56b8a2
commit d0c64188b6
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
HACKING
View File

@ -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, 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, 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 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, (guix-commits@gnu.org), so people can notice. Before pushing your changes,
make sure to run ‘git pull --rebase’. make sure to run ‘git pull --rebase’.