[Telepathy-commits] [telepathy-spec/master] open-issues.txt: link to request use-cases

[Simon McVittie]

20080627143326-53eee-274da0981bd75b635b90cdb159d5cd775167c1dc.gz
---
 doc/open-issues.txt |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/doc/open-issues.txt b/doc/open-issues.txt
index 0d99599..e7b7edb 100644
--- a/doc/open-issues.txt
+++ b/doc/open-issues.txt
@@ -13,15 +13,25 @@ is it OK to use observers for this?
 
 req1_: how do we tell the CM about our new vs existing requirements?
 
+.. _req1: request.html#req1
+
 req3_: can we safely disallow creating new channels with the wrong bundle ID?
 
+.. _req3: request.html#req3
+
 req26b_: mid-air collision where local and remote try to reopen the same
 conversation
 
+.. _req26b: request.html#req26b
+
 req5_: is this proposed implementation OK?
 
+.. _req5: request.html#req5
+
 req7_: how do chatroom threads work?
 
+.. _req7: request.html#req7
+
 dis2_: what happens when a Text channel-handler crashes?
 
 .. _dis2: dispatch.html#dis2
@@ -51,6 +61,9 @@ Minor/corner-case
 
 req29_, req30_: two contacts call each other simultaneously
 
+.. _req29: request.html#req29
+.. _req30: request.html#req30
+
 dis12_: how do we know when all groups have arrived?
 
 .. _dis12: dispatch.html#dis12
-- 
1.5.6.5