Regen.

[bison.git] / HACKING

diff --git a/HACKING b/HACKING
index 157d714583856d9acb066979e4f69d9061fde760..b661d88ef58134f0153fd9d75bffe3ce566e283f 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


@@ -46,11 +52,10 @@ release:
   that 1. Bison compiles cleanly, 2. the parsers it produces compile
   cleanly too.
 
   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
 
 - Change tests/atlocal/CFLAGS to add your preferred options.  For
   instance, `-traditional' to check that the parsers are K&R.  Note


@@ -58,8 +63,6 @@ release:
   but currently is actually GNU C, nor for lalr1.cc, which anyway is
   not exercised yet in the test suite.
 
   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
 
 
 * Release Procedure
 


@@ -104,13 +107,17 @@ In configure.ac.  Run `make', check this in.
 
 ** Announce
 Complete/fix the announcement file, and send it at least to
 
 ** Announce
 Complete/fix the announcement file, and send it at least to

-info@gnu.org (if a real release, or a ``serious beta''),
+info-gnu@gnu.org (if a real release, or a ``serious beta''),

 bison@gnu.org, and translation@iro.umontreal.ca.
 
 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.
+

 
 -----
 
 
 -----
 

-Copyright (C) 2002 Free Software Foundation, Inc.
+Copyright (C) 2002, 2003 Free Software Foundation, Inc.

 
 This file is part of GNU Bison.
 
 
 This file is part of GNU Bison.