From d89e2be91d79fca0a062744ff1dee630962cba7d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Jul 2010 14:16:36 -0400 Subject: [PATCH] response --- ...dir_should_be_under_control_of_RCS__63__.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/forum/recentchanges_dir_should_be_under_control_of_RCS__63__.mdwn b/doc/forum/recentchanges_dir_should_be_under_control_of_RCS__63__.mdwn index 69af04fe9..bef79335f 100644 --- a/doc/forum/recentchanges_dir_should_be_under_control_of_RCS__63__.mdwn +++ b/doc/forum/recentchanges_dir_should_be_under_control_of_RCS__63__.mdwn @@ -31,3 +31,19 @@ to find a reason of problem with my Ikiwiki? My best regards, Pawel +> No, the recentchanges pages are automatically generated and should not +> themselves be in revision control. +> +> Ikiwiki has recently started automatically enabing `--gettime`, but +> it should not do it every time, but only on the initial build +> of a wiki. It will print "querying svn for file creation and modification +> times.." when it does this. If it's doing it every time, something +> is wrong. (Specifically, `.ikiwiki/indexdb` must be missing somehow.) +> +> The support for svn with --gettime is rather poor. (While with git it is +> quite fast.) But as it's only supposed to happen on the first build, +> I haven't tried to speed it up. It would be hard to do it fast with svn. +> It would be possible to avoid the warning message above, or even skip +> processing files in directories not checked into svn -- but I'd much +> rather understand why you are seeing this happen on repeated builds. +> --[[Joey]] -- 2.32.0.93.g670b81a890