From d392f4db9d9bd53ec4acaa83090a47e6c2480ce2 Mon Sep 17 00:00:00 2001
From: Matthias Bolte <matthias.bolte@googlemail.com>
Date: Tue, 19 Jan 2010 21:39:20 +0100
Subject: [PATCH] docs: Remove outdated information about remote limitations

---
 docs/remote.html.in | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/docs/remote.html.in b/docs/remote.html.in
index 2716ebe2b0..b8b8f2bcd4 100644
--- a/docs/remote.html.in
+++ b/docs/remote.html.in
@@ -811,16 +811,6 @@ should just 'do the right thing(tm)'.
       <a name="Remote_limitations" id="Remote_limitations">Limitations</a>
     </h3>
     <ul>
-      <li> Remote storage: To be fully useful, particularly for
-creating new domains, it should be possible to enumerate
-and provision storage on the remote machine.  This is currently
-in the design phase. </li>
-      <li> Migration: We expect libvirt will support migration,
-and obviously remote support is what makes migration worthwhile.
-This is also in the design phase.  Issues <a href="https://www.redhat.com/mailman/listinfo/libvir-list" title="libvir-list mailing list">to discuss</a> include
-which path the migration data should follow (eg. client to
-client direct, or client to server to client) and security.
-</li>
       <li> Fine-grained authentication: libvirt in general,
 but in particular the remote case should support more
 fine-grained authentication for operations, rather than
-- 
GitLab