Don't include c.m4, as "include" doesn't do what we want.

[bison.git] / HACKING

diff --git a/HACKING b/HACKING
index fa20885a413c28a064347587b318b62e10d3f71e..bd83382af9a2b72480f8ca4eeec370c1925951b4 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -52,11 +52,10 @@ release:
   that 1. Bison compiles cleanly, 2. the parsers it produces compile
   cleanly too.
 
-- Change tests/bison to run `valgrind -q bison' to run Bison under
-  Valgrind.
-
-- Run the test suite with `./testsuite PREPARSER='valgrind -q' to make
-  sure the parser behave properly.
+- run `make maintainer-check' which:
+  - runs `valgrind -q bison' to run Bison under Valgrind.
+  - runs the parsers under Valgrind.
+  - runs the test suite with G++ as C compiler...
 
 - Change tests/atlocal/CFLAGS to add your preferred options.  For
   instance, `-traditional' to check that the parsers are K&R.  Note
@@ -64,8 +63,6 @@ release:
   but currently is actually GNU C, nor for lalr1.cc, which anyway is
   not exercised yet in the test suite.
 
-- Change tests/atlocal/CC to use a C++ compiler.
-
 
 * Release Procedure
 
@@ -113,6 +110,10 @@ Complete/fix the announcement file, and send it at least to
 info@gnu.org (if a real release, or a ``serious beta''),
 bison@gnu.org, and translation@iro.umontreal.ca.
 
+Send the same announcement on the comp.compilers newsgroup.  Do not
+make any Cc as the moderator will throw away anything cross-posted or
+Cc'ed.  It really needs to be a separate message.
+
 
 -----