maint: minor fixes

[bison.git] / README-hacking

diff --git a/README-hacking b/README-hacking
index cfb4b31207f50da2b07d8374a560a5517ca758a9..f128c9c5b2a9cc448f1da5b4f3d437da4d201b34 100644 (file)
--- a/README-hacking
+++ b/README-hacking
@@ -37,6 +37,13 @@ of the .output file etc.  This excludes impossible error messages
 (comparable to assert/abort), and all the --trace output which is
 meant for the maintainers only.
 
+** Horizontal tabs
+Do not add horizontal tab characters to any file in Bison's repository
+except where required.  For example, do not use tabs to format C code.
+However, make files, ChangeLog, and some regular expressions require
+tabs.  Also, test cases might need to contain tabs to check that Bison
+properly processes tabs in its input.
+
 
 * Working from the repository
 
@@ -211,6 +218,9 @@ release:
   that it does not make sense for glr.c, which should be ANSI, but
   currently is actually GNU C, nor for lalr1.cc.
 
+- Test with a very recent version of GCC for both C and C++.  Testing
+  with older versions that are still in use is nice too.
+
 
 * Release Procedure
 This section needs to be updated to take into account features from
@@ -249,7 +259,10 @@ that the skeletons insert into generated parsers, and check all
 occurrences of PACKAGE_COPYRIGHT_YEAR in configure.ac.
 
 ** Update NEWS, commit and tag.
-See do-release-commit-and-tag in README-release.
+See do-release-commit-and-tag in README-release.  For a while, we used
+beta names such as "2.6_rc1".  Now that we use gnulib in the release
+procedure, we must use "2.5.90", which has the additional benefit of
+being properly sorted in "git tag -l".
 
 ** make alpha, beta, or stable
 See README-release.
@@ -272,7 +285,7 @@ where F125BDF3 should be replaced with your key ID.
 *** Using gnupload
 You need "ncftp".
 
-At the end "make stable" (or alpha/beta) will display the prodecure to
+At the end "make stable" (or alpha/beta) will display the procedure to
 run.  Just copy and paste it in your shell.
 
 *** By hand