aboutsummaryrefslogtreecommitdiff
path: root/doc/features.mdwn
diff options
context:
space:
mode:
authorwww-data <www-data@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-03-11 05:47:47 +0000
committerwww-data <www-data@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-03-11 05:47:47 +0000
commit11ec8618555fe8a89dbdaa9ac73260d9b81ae086 (patch)
tree7f716054db1b5b6749b078ba06b428cc083dda11 /doc/features.mdwn
parent169162e92f06e2fad4c4a18c0ec45e5643a4c595 (diff)
downloadikiwiki-11ec8618555fe8a89dbdaa9ac73260d9b81ae086.tar
ikiwiki-11ec8618555fe8a89dbdaa9ac73260d9b81ae086.tar.gz
web commit from 66.118.98.137:
Diffstat (limited to 'doc/features.mdwn')
-rw-r--r--doc/features.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/features.mdwn b/doc/features.mdwn
index 069be981a..8ba65fc55 100644
--- a/doc/features.mdwn
+++ b/doc/features.mdwn
@@ -4,7 +4,7 @@ Currently implemented:
Rather than implement its own system for storing page histories etc, ikiwiki simply uses subversion. (Supporting other revision control systems is also possible, ikiwiki only needs $FOO add, $FOO commit, and $FOO log).
- Instead of editing pages in a stupid web form, you can use vim and commit changes via svn. Or work disconnected using svk and push your changes out when you come online.
+ Instead of editing pages in a stupid web form, you can use vim and commit changes via svn. Or work disconnected using svk and push your changes out when you come online. Deal with edit conflicts with others in a sane environment. Take advantage of subversion's smart merges.
ikiwiki can be run from a [[post-commit]] hook to update your wiki immediatly whenever you commit.