bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] Version 2.4.2.


From: Joel E. Denny
Subject: [PATCH] Version 2.4.2.
Date: Sat, 20 Mar 2010 15:16:30 -0400 (EDT)
User-agent: Alpine 1.00 (DEB 882 2007-12-20)

I pushed this to branch-2.4.2, branch-2.5, and master.  I also pushed a 
v2.4.2 tag, and I regenerated the html manual into CVS.

It bothers me that branch-2.5:ChangeLog and master:ChangeLog now have an 
entry that says "Version 2.4.2" but that is more recent than many 
ChangeLog entries that do not appear in release 2.4.2.  What's the normal 
way of handling this?

>From 08090fe64c2956a4211fb5f6fd40762fe1f198b5 Mon Sep 17 00:00:00 2001
From: Joel E. Denny <address@hidden>
Date: Sat, 20 Mar 2010 13:10:09 -0400
Subject: [PATCH] Version 2.4.2.

* NEWS (2.4.2): Set version and date.  For the recent test suite
portability fixes, don't be so optimistic about their success
given the lack of feedback on the affected platforms.
---
 ChangeLog |    7 +++++++
 NEWS      |    6 +++---
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index b36fe7c..d0209b6 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2010-03-20  Joel E. Denny  <address@hidden>
+
+       Version 2.4.2.
+       * NEWS (2.4.2): Set version and date.  For the recent test suite
+       portability fixes, don't be so optimistic about their success
+       given the lack of feedback on the affected platforms.
+
 2010-02-22  Joel E. Denny  <address@hidden>
 
        Prepare for 2.4.2 release.
diff --git a/NEWS b/NEWS
index f11844d..63f8cde 100644
--- a/NEWS
+++ b/NEWS
@@ -1,12 +1,12 @@
 Bison News
 ----------
 
-* Changes in version 2.4.2 (????-??-??):
+* Changes in version 2.4.2 (2010-03-20):
 
 ** Some portability problems that resulted in failures and livelocks
    in the test suite on some versions of at least Solaris, AIX, HP-UX,
-   RHEL4, and Tru64 have been fixed.  As part of those fixes, fatal
-   Bison errors no longer cause M4 to report a broken pipe on the
+   RHEL4, and Tru64 have been addressed.  As a result, fatal Bison
+   errors should no longer cause M4 to report a broken pipe on the
    affected platforms.
 
 ** `%prec IDENTIFIER' requires IDENTIFIER to be defined separately.
-- 
1.5.4.3





reply via email to

[Prev in Thread] Current Thread [Next in Thread]