Optimize away most expensive file prune calls, when refreshing

[git.ikiwiki.info.git] / doc / bugs / diff_links_to_backtrace.mdwn

diff --git a/doc/bugs/diff_links_to_backtrace.mdwn b/doc/bugs/diff_links_to_backtrace.mdwn
index 16f84fafbccd181312b541a36c377156b633862d..0a361aa246be095d04219dcb27b71d4549ff83cf 100644 (file)
--- a/doc/bugs/diff_links_to_backtrace.mdwn
+++ b/doc/bugs/diff_links_to_backtrace.mdwn
@@ -1,5 +1,9 @@
-The diff links in RecentChanges go to a viewcvs backtrace if the rev in 
-question is when the page was added. Is this a viewcvs bug, or a behavior 
+The diff links in RecentChanges go to a viewvc backtrace if the rev in 
+question is when the page was added. Is this a viewvc bug, or a behavior 

 ikiwiki needs to work around?
   - As a special case, there should certianly be no history link for
     pages generated from the underlaydir as it can never work for them.
 ikiwiki needs to work around?
   - As a special case, there should certianly be no history link for
     pages generated from the underlaydir as it can never work for them.

+
+Hmm, gitweb deals with this ok, and can even handle the case where a page
+was renamed from some other filename. So I don't think it's appropriate
+for ikiwiki to worry about this. [[done]] --[[Joey]]