1.0.8.16: really increment the fasl version

 (file left out from previous commit)

diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp
index 10da6e4..a051605 100644 (file)
--- a/src/code/early-fasl.lisp
+++ b/src/code/early-fasl.lisp
@@ -76,7 +76,7 @@
 ;;; versions which break binary compatibility. But it certainly should
 ;;; be incremented for release versions which break binary
 ;;; compatibility.
-(def!constant +fasl-file-version+ 74)
+(def!constant +fasl-file-version+ 75)
 ;;; (description of versions before 0.9.0.1 deleted in 0.9.17)
 ;;; 56: (2005-05-22) Something between 0.9.0.1 and 0.9.0.14. My money is
 ;;;     on 0.9.0.6 (MORE CASE CONSISTENCY).
@@ -104,6 +104,7 @@
 ;;; 72: (2006-12-05) Added slot to the primitive function type
 ;;; 73: (2007-04-13) Changed a hash function
 ;;; 74: (2007-06-05) UNWIND-TO-FRAME-AND-CALL
+;;; 75: (2007-08-06) FD-STREAM layout changes
 
 ;;; the conventional file extension for our fasl files
 (declaim (type simple-string *fasl-file-type*))

diff --git a/version.lisp-expr b/version.lisp-expr
index 8f7478a..b88d052 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.8.16"
+"1.0.8.17"