From 020eb6f294346a3a5db5d04b7d14cb30ddd4bfaf Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 15 Oct 2008 19:32:39 -0400 Subject: response --- doc/bugs/disabling_backlinks.mdwn | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'doc/bugs') diff --git a/doc/bugs/disabling_backlinks.mdwn b/doc/bugs/disabling_backlinks.mdwn index 9c31b6030..ba96a4e2b 100644 --- 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]] -- cgit v1.2.3