dépôts
/
lhc
/
web
/
wiklou.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
ec5a8e0
)
* eg => e.g.
author
Ævar Arnfjörð Bjarmason
<avar@users.mediawiki.org>
Mon, 2 May 2005 04:22:14 +0000
(
04:22
+0000)
committer
Ævar Arnfjörð Bjarmason
<avar@users.mediawiki.org>
Mon, 2 May 2005 04:22:14 +0000
(
04:22
+0000)
UPGRADE
patch
|
blob
|
history
diff --git
a/UPGRADE
b/UPGRADE
index
8548527
..
4449ffa
100644
(file)
--- a/
UPGRADE
+++ b/
UPGRADE
@@
-1,11
+1,11
@@
== The basic theory ==
== The basic theory ==
-Generally, within a stable release series (e
g
1.4.0, 1.4.1, etc) there
+Generally, within a stable release series (e
.g.
1.4.0, 1.4.1, etc) there
are no required database changes, and upgrading should require no more
than copying the new source files over the old ones.
If there are larger changes, such as upgrading from one release series
are no required database changes, and upgrading should require no more
than copying the new source files over the old ones.
If there are larger changes, such as upgrading from one release series
-to another (e
g
from 1.3.12 to 1.4.3), then you may need to update the
+to another (e
.g.
from 1.3.12 to 1.4.3), then you may need to update the
database schema and configuration.
Basically, to upgrade a wiki you:
database schema and configuration.
Basically, to upgrade a wiki you: