(bitset_op4_cmp): Supply prototype decls,

[bison.git] / HACKING

diff --git a/HACKING b/HACKING
index 157d714583856d9acb066979e4f69d9061fde760..fa20885a413c28a064347587b318b62e10d3f71e 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -4,6 +4,11 @@ This file attempts to describe the rules to use when hacking Bison.
 Don't put this file into the distribution.  Don't mention it in the
 ChangeLog.
 
 Don't put this file into the distribution.  Don't mention it in the
 ChangeLog.
 

+Everything related to the development of Bison is on Savannah:
+
+       http://savannah.gnu.org/projects/bison/
+
+

 * Administrivia
 
 ** If you incorporate a change from somebody on the net:
 * Administrivia
 
 ** If you incorporate a change from somebody on the net:


@@ -21,6 +26,7 @@ The correct response to most actual bugs is to write a new test case
 which demonstrates the bug.  Then fix the bug, re-run the test suite,
 and check everything in.
 
 which demonstrates the bug.  Then fix the bug, re-run the test suite,
 and check everything in.
 

+

 * Hacking
 
 ** Visible changes
 * Hacking
 
 ** Visible changes