projects
/
mir.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
48b18c6
)
add a note about consulting the NEWS file
author
mh
<mh>
Sat, 7 Dec 2002 06:57:40 +0000
(06:57 +0000)
committer
mh
<mh>
Sat, 7 Dec 2002 06:57:40 +0000
(06:57 +0000)
doc/UPGRADING.mir
patch
|
blob
|
history
diff --git
a/doc/UPGRADING.mir
b/doc/UPGRADING.mir
index
ab387a0
..
67ddd43
100755
(executable)
--- a/
doc/UPGRADING.mir
+++ b/
doc/UPGRADING.mir
@@
-1,6
+1,12
@@
MIR UPGRADING HOWTO
----------------------------------------------------------------
MIR UPGRADING HOWTO
----------------------------------------------------------------
+For releases after 1.0.0-rc1, always check the NEWS file at the root of the
+tree to check the [Notes] section to see what you might have to adjust.
+
+For non releases or releases before 1.0.0-rc1, aka. the latest sources from
+CVS, it is a good idea to follow the advice below.
+
Due to weaknesses of the current Mir configuration system, many folks get
bitten after doing an update of their cvs tree. Suddenly Mir starts throwing
weird exceptions, etc.. The cause is usually a new config option in the
Due to weaknesses of the current Mir configuration system, many folks get
bitten after doing an update of their cvs tree. Suddenly Mir starts throwing
weird exceptions, etc.. The cause is usually a new config option in the
@@
-20,4
+26,4
@@
config.properties file and modify if necessary.
----------------------------------------------------------------
----------------------------------------------------------------
-
$Date: 2002/07/03 12:09:2
0 $ - the Mir coders
+
last changed: $Date: 2002/12/07 06:57:4
0 $ - the Mir coders