diff options
| author | Ludovic Courtès <ludo@gnu.org> | 2013-08-26 22:23:53 +0200 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2013-08-26 22:23:53 +0200 |
| commit | 2d2ad9891046ffd71efef0d2e5aa883e6f87fd9e (patch) | |
| tree | b0ffcc5ecb4dddb73c0df282cead01bad4766300 /HACKING | |
| parent | 9c629a27a435dd37b55a3944f8d79accc710a0e4 (diff) | |
doc: Change `HACKING' to refer to guix-devel@gnu.org.
Reported by Alex Sassmannshausen <alex.sassmannshausen@gmail.com>.
* HACKING: Replace "bug-guix" by "guix-devel".
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 8 |
1 files changed, 4 insertions, 4 deletions
| @@ -127,7 +127,7 @@ expression” of Nettle. | |||
| 127 | Development is done using the Git distributed version control system. Thus, | 127 | Development is done using the Git distributed version control system. Thus, |
| 128 | access to the repository is not strictly necessary. We welcome contributions | 128 | access to the repository is not strictly necessary. We welcome contributions |
| 129 | in the form of patches as produced by ‘git format-patch’ sent to | 129 | in the form of patches as produced by ‘git format-patch’ sent to |
| 130 | bug-guix@gnu.org. Please write commit logs in the [[http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs][GNU ChangeLog format]]. | 130 | guix-devel@gnu.org. Please write commit logs in the [[http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs][GNU ChangeLog format]]. |
| 131 | 131 | ||
| 132 | As you become a regular contributor, you may find it convenient to have write | 132 | As you become a regular contributor, you may find it convenient to have write |
| 133 | access to the repository (see below.) | 133 | access to the repository (see below.) |
| @@ -137,9 +137,9 @@ access to the repository (see below.) | |||
| 137 | For frequent contributors, having write access to the repository is | 137 | For frequent contributors, having write access to the repository is |
| 138 | convenient. When you deem it necessary, feel free to ask for it on the | 138 | convenient. When you deem it necessary, feel free to ask for it on the |
| 139 | mailing list. When you get commit access, please make sure to follow the | 139 | mailing list. When you get commit access, please make sure to follow the |
| 140 | policy below (discussions of the policy can take place on bug-guix@gnu.org.) | 140 | policy below (discussions of the policy can take place on guix-devel@gnu.org.) |
| 141 | 141 | ||
| 142 | Non-trivial patches should always be posted to bug-guix@gnu.org (trivial | 142 | Non-trivial patches should always be posted to guix-devel@gnu.org (trivial |
| 143 | patches include fixing typos, etc.) | 143 | patches include fixing typos, etc.) |
| 144 | 144 | ||
| 145 | For patches that just add a new package, and a simple one, it’s OK to commit, | 145 | For patches that just add a new package, and a simple one, it’s OK to commit, |
| @@ -149,7 +149,7 @@ package upgrades. We have a mailing list for commit notifications | |||
| 149 | (guix-commits@gnu.org), so people can notice. Before pushing your changes, | 149 | (guix-commits@gnu.org), so people can notice. Before pushing your changes, |
| 150 | make sure to run ‘git pull --rebase’. | 150 | make sure to run ‘git pull --rebase’. |
| 151 | 151 | ||
| 152 | For anything else, please post to bug-guix@gnu.org and leave time for a | 152 | For anything else, please post to guix-devel@gnu.org and leave time for a |
| 153 | review, without committing anything. If you didn’t receive any reply | 153 | review, without committing anything. If you didn’t receive any reply |
| 154 | after two weeks, and if you’re confident, it’s OK to commit. | 154 | after two weeks, and if you’re confident, it’s OK to commit. |
| 155 | 155 | ||