From c8537b41320e1f38b2369f24431423dfb2f14b15 Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Thu, 4 Nov 2010 10:58:53 +0000 Subject: [PATCH] --- doc/forum/Blog_posting_times_and_ikiwiki_state.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) 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]] -- 2.32.0.93.g670b81a890