aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-05-19 13:54:34 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-05-19 13:54:34 -0400
commit8973f0a6e31ad5db325fcdee2c875dd029673dad (patch)
tree794ff18566c9e36423de4b86acb70c3c8f3a0afd
parentdaed5ead7dd21363c9456c363384e78bde549c5f (diff)
downloadikiwiki-8973f0a6e31ad5db325fcdee2c875dd029673dad.tar
ikiwiki-8973f0a6e31ad5db325fcdee2c875dd029673dad.tar.gz
correction; unchanged pages not rescanned
-rw-r--r--doc/todo/inlines_inheriting_links.mdwn12
1 files changed, 3 insertions, 9 deletions
diff --git a/doc/todo/inlines_inheriting_links.mdwn b/doc/todo/inlines_inheriting_links.mdwn
index 56f18418d..c53da51c5 100644
--- a/doc/todo/inlines_inheriting_links.mdwn
+++ b/doc/todo/inlines_inheriting_links.mdwn
@@ -34,12 +34,6 @@ I would actually use it in my current "project" in ikiwiki: I actually edit a se
> So to tell what they link to, inline would have to load
> each of them, and scan them.
>
-> And that would happen on *every* build of the wiki,
-> even if the page with the inline didn't change. So
-> there's the potential for this to really badly slow
-> down a wiki build.
->
-> Maybe there's the potential to add some really smart
-> caching code that avoids unnecessary re-scanning
-> and is really quick.. but I suspect it would be *very*
-> complex too. --[[Joey]]
+> So there's the potential for this to slow
+> down a wiki build by about a factor of 2.
+> --[[Joey]]