response

diff --git a/doc/bugs/disabling_backlinks.mdwn b/doc/bugs/disabling_backlinks.mdwn
index 9c31b603059f58296d7181d8e9bcc7ddb2f07e9c..ba96a4e2b5203e86e493a66d0162434901b2ece7 100644 (file)
--- a/doc/bugs/disabling_backlinks.mdwn
+++ b/doc/bugs/disabling_backlinks.mdwn
@@ -14,6 +14,17 @@ My first reading (and second and third) of this was that backlinks would be disa
 > improve the documentation for this. [[done]] --[[Joey]]
 
 
-I notice that there is quite a bit of redundancy when both tags and backlinks are used extensively. On most pages, the set of links features in both categories is almost identical because a tag's index page is shown both as a tag link and as a backlink. Is there a way to improve that situation somehow? I realise that backlinks aren't generated when the tag index page refers to its contents by \[\[!map ...]], etc., but sometimes an auto-generated index is insufficient.
+I notice that there is quite a bit of redundancy when both tags and
+backlinks are used extensively. On most pages, the set of links features in
+both categories is almost identical because a tag's index page is shown
+both as a tag link and as a backlink. Is there a way to improve that
+situation somehow? I realise that backlinks aren't generated when the tag
+index page refers to its contents by \[\[!map ...]], etc., but sometimes an
+auto-generated index is insufficient.
 
  --Peter
+
+> Um, if you're manually linking from the tag's page to each page so
+> tagged, I think you have larger problems than tags and backlinks being
+> the same. Like keeping that list of links up to date as tags are added
+> and changed. --[[Joey]]