X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fearly-fasl.lisp;h=6c60a2af2c3cc07607c6a3562776d3326363bf76;hb=d720bc359f03734ccb9baf66cb45dc01d623f369;hp=2249dd127448f4ea390abb803ea045e1bab2326e;hpb=a2b7a6a58e894c02cff583d2d7d1b971a53d7c2d;p=sbcl.git

diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp
index 2249dd1..6c60a2a 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+ 77)
+(def!constant +fasl-file-version+ 78)
 ;;; (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).
@@ -112,6 +112,8 @@
 ;;;     Further fasl-file-version bumps should only be done for real changes
 ;;;     in the fasl format, not for changes in function/macro signatures or
 ;;;     lisp data structures.
+;;; 78: (2010-04-02) Add FOP-{SMALL-,}NAMED-PACKAGE, remove FOP-NORMAL-LOAD
+;;;     and FOP-MAYBE-COLD-LOAD.
 
 ;;; the conventional file extension for our fasl files
 (declaim (type simple-string *fasl-file-type*))