diff options
| author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2006-03-26 02:30:44 +0000 |
|---|---|---|
| committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2006-03-26 02:30:44 +0000 |
| commit | 90923561734f17ad777237bed5e7b40e682344eb (patch) | |
| tree | 8d1ef394472f0e36f167dc5683c6d368b2cb61d2 /doc | |
| parent | 3903c2ce3a72d1fcd941f0e24a6780eaf15aa33a (diff) | |
added --getctime
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/security.mdwn | 4 | ||||
| -rw-r--r-- | doc/todo/blogging.mdwn | 8 | ||||
| -rw-r--r-- | doc/usage.mdwn | 7 |
3 files changed, 11 insertions, 8 deletions
diff --git a/doc/security.mdwn b/doc/security.mdwn index c7a6fcd69..48d82db89 100644 --- a/doc/security.mdwn +++ b/doc/security.mdwn @@ -46,7 +46,9 @@ this wiki, BTW. Anyone with svn commit access can forge "web commit from foo" and make it appear on [[RecentChanges]] like foo committed. One way to avoid this would be to limit web commits to those done by a certian user. -It's actually possible to force a whole series of svn commits to appear to have come just before yours, by forging svn log output. This could be guarded against somewhat by revision number scanning, since the forged revisions would duplicate the numbers of unforged ones. Or subversion could fix svn log to indent commit messages, which would make such forgery impossible.. +It's actually possible to force a whole series of svn commits to appear to +have come just before yours, by forging svn log output. This could be +guarded against by using svn log --xml. ikiwiki escapes any html in svn commit logs to prevent other mischief. diff --git a/doc/todo/blogging.mdwn b/doc/todo/blogging.mdwn index 7d89a9904..680570d84 100644 --- a/doc/todo/blogging.mdwn +++ b/doc/todo/blogging.mdwn @@ -3,10 +3,4 @@ - The [[TODO]] page would work better if the first N were shown in full, and then all open items were shown in summary. Maybe add this mode. - Add Discussion and Edit links at the bottom of each inlined post. -- Still not completly comfortable with ikiwiki only knowing when a page was - posted based on the on-disk mtime the first time it sees the page. svn doesn't - preserve mtimes and also if the index gets broken it will see new mtimes for any - pages that were actually modified in the interim. I suppose that info could - be pulled out of svn log by a utility that was run if the index or mtimes - got screwed up. -- It would be possible to support rss enclosures for eg, podcasts, pretty easily.
\ No newline at end of file +- It would be possible to support rss enclosures for eg, podcasts, pretty easily. diff --git a/doc/usage.mdwn b/doc/usage.mdwn index f36886d75..aa4978773 100644 --- a/doc/usage.mdwn +++ b/doc/usage.mdwn @@ -30,6 +30,13 @@ flags such as --verbose can be negated with --no-verbose. Force a rebuild of all pages. +* --fixctime + + Pull last changed time for all pages out of the revision control system. + This rarely used option provides a way to get the real creation times of + items in weblogs, for example when building a wiki from a new subversion + checkout. It is unoptimised and quite slow. + * --templatedir Specify the directory that the page [[templates]] are stored in. |