From f236e2ccab39167e589433bb346f4e214043444f Mon Sep 17 00:00:00 2001 From: William Harold Newman Date: Mon, 14 Aug 2006 13:07:50 +0000 Subject: [PATCH] 0.9.15.30: incremented +FASL-FILE-VERSION+ --- src/code/early-fasl.lisp | 3 ++- version.lisp-expr | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 01a78c3..09c3333 100644 --- 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+ 67) +(def!constant +fasl-file-version+ 68) ;;; (record of versions before 2003 deleted in 2003-04-26/0.pre8.107 or so) ;;; 38: (2003-01-05) changed names of internal SORT machinery ;;; 39: (2003-02-20) in 0.7.12.1 a slot was added to @@ -138,6 +138,7 @@ ;;; 66: (2006-05-13) Fopcompiler ;;; 67: (2006-07-25) Reports on #lisp about 0.9.13 fasls being invalid on ;;; 0.9.14.something +;;; 68: (2006-08-14) changed number of arguments of LOAD-DEFMETHOD ;;; 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 758804f..309ead2 100644 --- 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".) -"0.9.15.29" +"0.9.15.30" -- 1.7.10.4