[Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.6-120-ga94e7d8

[Mark H Weaver]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Guile".

http://git.savannah.gnu.org/cgit/guile.git/commit/?id=a94e7d85dd98893cebdb6108f3e7a7afb1e784dd

The branch, stable-2.0 has been updated
       via  a94e7d85dd98893cebdb6108f3e7a7afb1e784dd (commit)
      from  13fac28218b42fc5408ce62b64ae3d09c95cd91e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a94e7d85dd98893cebdb6108f3e7a7afb1e784dd
Author: Mark H Weaver <address@hidden>
Date:   Thu Nov 29 17:25:21 2012 -0500

    Minor fixes in NEWS
    
    * NEWS: Minor fixes to the descriptions.

-----------------------------------------------------------------------

Summary of changes:
 NEWS |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/NEWS b/NEWS
index c20a01a..daa7201 100644
--- a/NEWS
+++ b/NEWS
@@ -61,10 +61,10 @@ ways.
 First, the `LD_LIBRARY_PATH' modification would be visible to
 sub-processes, and would also affect future calls to `dlopen', which
 could lead to subtle bugs in the application or sub-processes.  Second,
-when the installation prefix is /usr/local, the `LD_LIBRARY_PATH'
-modification would typically end up inserting /usr/lib before
-/usr/local/lib in the search path, which is often the opposite of
-system-wide settings such as `ld.so.conf'.
+when the installation prefix is /usr, the `LD_LIBRARY_PATH' modification
+would typically end up inserting /usr/lib before /usr/local/lib in the
+search path, which is often the opposite of system-wide settings such as
+`ld.so.conf'.
 
 Both issues have now been fixed.
 
@@ -77,10 +77,10 @@ Programs should instead use `make-vtable' and 
`<standard-vtable>'.
 These recently introduced warnings have been documented and are now
 enabled by default when auto-compiling.
 
-** Optimize calls to `equal?' with a constant argument
+** Optimize calls to `equal?' or `eqv?' with a constant argument
 
-The compiler simplifies calls to `equal?' with a constant argument to
-use `eq?' or `eqv?' instead, when applicable.
+The compiler simplifies calls to `equal?' or `eqv?' with a constant
+argument to use `eq?' instead, when applicable.
 
 * Manual updates
 


hooks/post-receive
-- 
GNU Guile