aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://smcv.pseudorandom.co.uk/ <smcv@web>2010-11-04 10:58:53 +0000
committerJoey Hess <joey@kitenet.net>2010-11-04 10:58:53 +0000
commitc8537b41320e1f38b2369f24431423dfb2f14b15 (patch)
tree7cadb021dc7aa6d988a602b00b0c24e7823a7089
parent23e3e5f15e61639ccba4a7dfbab11d6fe4b9f047 (diff)
downloadikiwiki-c8537b41320e1f38b2369f24431423dfb2f14b15.tar
ikiwiki-c8537b41320e1f38b2369f24431423dfb2f14b15.tar.gz
-rw-r--r--doc/forum/Blog_posting_times_and_ikiwiki_state.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/forum/Blog_posting_times_and_ikiwiki_state.mdwn b/doc/forum/Blog_posting_times_and_ikiwiki_state.mdwn
index 3e6c23241..0c1da5b97 100644
--- a/doc/forum/Blog_posting_times_and_ikiwiki_state.mdwn
+++ b/doc/forum/Blog_posting_times_and_ikiwiki_state.mdwn
@@ -17,3 +17,12 @@ What can I do?
Is it a spectacularly bad idea to include the ikiwiki state file in my cloned repo (I suspect it is). What else could be done? Can I disable pagestate somehow or force ikiwiki to always use git commit times for Posted times?
+> Have you tried running ikiwiki with the `--gettime` option on your laptop,
+> to force it to retrieve initial commit times from git? You should only
+> need to do that once, and it'll be cached in the pagestate thereafter.
+>
+> Because that functionality is slow on every supported VCS except git,
+> ikiwiki tries to avoid using it unless it's really needed. [[rcs]]
+> lists it as "fast" for git, though, so depending how fast it really is
+> and how large your wiki is, you might be able to get away with running
+> ikiwiki with `--gettime` all the time? --[[smcv]]