| HACKING (54427) | HACKING (66525) |
|---|---|
| 1How to write code for CVS 2 3* Compiler options 4 5If you are using GCC, you'll want to configure with -Wall, which can 6detect many programming errors. This is not the default because it 7might cause spurious warnings, but at least on some machines, there 8should be no spurious warnings. For example: --- 177 unchanged lines hidden (view full) --- 186 also in DEVEL-CVS. 187 commit-cvs. The only messages sent to this list are sent 188 automatically, via the CVS `loginfo' mechanism, when someone 189 checks something in to the master CVS repository. 190 test-results. The only messages sent to this list are sent 191 automatically, daily, by a script which runs "make check" 192 and "make remotecheck" on the master CVS sources. 193To subscribe to devel-cvs, commit-cvs, or test-results, send | 1How to write code for CVS 2 3* Compiler options 4 5If you are using GCC, you'll want to configure with -Wall, which can 6detect many programming errors. This is not the default because it 7might cause spurious warnings, but at least on some machines, there 8should be no spurious warnings. For example: --- 177 unchanged lines hidden (view full) --- 186 also in DEVEL-CVS. 187 commit-cvs. The only messages sent to this list are sent 188 automatically, via the CVS `loginfo' mechanism, when someone 189 checks something in to the master CVS repository. 190 test-results. The only messages sent to this list are sent 191 automatically, daily, by a script which runs "make check" 192 and "make remotecheck" on the master CVS sources. 193To subscribe to devel-cvs, commit-cvs, or test-results, send |
| 194a message to "majordomo@cyclic.com" whose body consists of | 194a message to "majordomo@cvshome.org" whose body consists of |
| 195"subscribe <list>", where <list> is devel-cvs, commit-cvs or 196test-results. 197 198One other list related to CVS development is bug-cvs. This is the 199list which users are requested to send bug reports to. Anyone can 200subscribe; to do so send mail to bug-cvs-request@gnu.org. 201 202Other CVS discussions take place on the info-cvs mailing list 203(send mail to info-cvs-request@gnu.org to subscribe) or on 204the newsgroup comp.software.config-mgmt. | 195"subscribe <list>", where <list> is devel-cvs, commit-cvs or 196test-results. 197 198One other list related to CVS development is bug-cvs. This is the 199list which users are requested to send bug reports to. Anyone can 200subscribe; to do so send mail to bug-cvs-request@gnu.org. 201 202Other CVS discussions take place on the info-cvs mailing list 203(send mail to info-cvs-request@gnu.org to subscribe) or on 204the newsgroup comp.software.config-mgmt. |