summaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-08-01 17:35:55 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-08-01 17:39:17 -0400
commitbc1c26772384e8cb2a39176e5b7894739aa01104 (patch)
tree9cac0cd37fec92b23b8287239ffe21dbfe485789 /doc/bugs
parent190a845fe1ab44d3947f2ecdc0305a180e21e6f2 (diff)
response
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/recentchanges_feed_links.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/recentchanges_feed_links.mdwn b/doc/bugs/recentchanges_feed_links.mdwn
index 41d7719ea..9a5627ec4 100644
--- a/doc/bugs/recentchanges_feed_links.mdwn
+++ b/doc/bugs/recentchanges_feed_links.mdwn
@@ -39,3 +39,16 @@ to turn on? --Chapman Flack
>>>> and the inline plugin would then generate working links in feeds? How should
>>>> the guid be constructed? Something based on the rcs revision number? I guess
>>>> I'm still not completely clear on your vision for how it ought to work. --Chap
+
+>>>> My idea is to use `\[[meta guid="http://url/recentchanges#rev"]]`, with the
+>>>> `#rev` anchor also included in the change file, and being the rcs's
+>>>> internal revision id. Then the guid is globally unique, and actually
+>>>> links to the change in the recentchanges page. And, when the change
+>>>> has fallen off the page, the link will still go to the recentchanges page.
+>>>>
+>>>> First, need to check that guids in rss and atom feeds can have anchors in
+>>>> them, and that the anchor is treated as part of the guid. (If the guid
+>>>> is interpreted as just "http://url/recentchanges", then it's
+>>>> not a very good guid.) If using an anchor for a guid is a problem,
+>>>> it could instead generate a random uuid, and use `\[[meta
+>>>> guid="urn:uuid:<foo>" permalink="http://url/recentchanges"]]`