*** empty log message ***

INSTALL

@@ -75,15 +75,15 @@ be enabled by default.  The interaction with blocking I/O is pretty ad
 hoc at the moment.  In our experience, bugs in the thread support do
 not affect you if you don't actually use threads.
 
-At the moment, threads are known not to work with the NetBSD 1.2
-assembler.
-
 --enable-dynamic-linking --- Build a Guile executable and library
 providing Scheme functions which can load a shared library and
 initialize it, perhaps thereby adding new functions to Guile.  This
-feature is not yet thoroughly tested; once it is, it will be enabled
-by default.  This option has no effect on systems that do not support
-shared libraries.
+feature is enabled by default; you only need to use this option (as
+`--enable-dynamic-linking=no') if you want to build a Guile which does
+not support dynamic linking.
+
+This option has no effect on systems that do not support shared
+libraries.
 
 --disable-shared --- Do not build shared libraries.  Normally, Guile
 will build shared libraries if your system supports them.  Guile

NEWS

@@ -263,6 +263,14 @@ True iff OBJ is a macro object.
 Like (macro? OBJ), but true only if OBJ is one of the Guile primitive
 macro transformers, implemented in eval.c rather than Scheme code.
 
+Why do we have this function?
+- For symmetry with procedure? and primitive-procedure?,
+- to allow custom print procedures to tell whether a macro is
+  primitive, and display it differently, and
+- to allow compilers and user-written evaluators to distinguish
+  builtin special forms from user-defined ones, which could be
+  compiled.
+
 *** New function: (macro-type OBJ)
 Return a value indicating what kind of macro OBJ is.  Possible return
 values are:

RELEASE

@@ -26,13 +26,14 @@ HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
 2) Verify that Guile builds and runs in your working directory.  I
    hope that we'll eventually have a test suite to make this more
    concrete, but for the moment, just make sure things seem sane.
-3) Make sure NEWS and the docs are up to date:
+3) Make sure NEWS, INSTALL and the docs are up to date:
    a) Scan the ChangeLogs for user-visible changes, marked with an asterisk
       at the left margin.
    b) Update NEWS and the Texinfo documentation as appropriate.
    c) Remove the user-visible markers from the log entries once they're
       documented.
    d) Check for any [[incomplete]] sections of NEWS.
+   e) Fact-check INSTALL.
 4) Scan output from `cvs diff' to find files that have changed a lot, but
    do not have up-to-date copyright notices.
 5) Update the version numbers in GUILE-VERSION, and README.  The Guile
@@ -62,9 +63,8 @@ HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
     g) If you made any fixes, commit them, and start from a) again
 11a) Add "Guile N.M released." entry to ChangeLog, and commit it.
 12) Tag the entire source tree with a tag of the form "release_N_M".
-13) Copy the tar file over to the GNU machines, and ask the appropriate
-    person to put it on prep.  At the time of this writing, Joel Weber
-    <devnull@gnu.org> has been generous about helping with that.
+13) Copy the tar file over to the GNU machines, and send mail to
+    ftp-upload@gnu.org, asking them to put it on prep.
 14) Send an announcement message to gnu-announce@gnu.org.  Put
     "Obtaining Guile" first, then a brief summary of the changes in
     this release, then "Thanks," "About This Distribution," and