Move the discussion of svn+ssh to the forum for now.

diff --git a/doc/rcs/svn/discussion.mdwn b/doc/rcs/svn/discussion.mdwn
index 887b5c4a28254284c44b6f8cab65f513bbbf6849..426735182cac57517c775d686c42eb951151b128 100644 (file)
--- a/doc/rcs/svn/discussion.mdwn
+++ b/doc/rcs/svn/discussion.mdwn
@@ -11,17 +11,3 @@ can act upon them sequentially, or (2) optionally divorce the `ikiwiki
 I'm not aware of web servers, at least apache, killing cgi processes when
 the user stops a page load. If this is happening ikiwiki should be able to
 avoid it by blocking whatever signal is causing it to terminate. --[[Joey]]
-
-Just as an experiment, I tried running ikiwiki using a *remote* repository,
-i.e. via "svn+ssh".  After setting up the repo and relocating the working copy,
-unfortunately, it doesn't work; editing a page gives the error:
-
-Error: no element found at line 3, column 0, byte 28 at /opt/local/lib/perl5/vendor_perl/5.10.1/darwin-multi-2level/XML/Parser.pm line 187
-
-I *think* this is because, despite a SetEnv directive in the apache configuration,
-the CGI wrapper is expunging SVN_SSH from the environment (based on perusing
-the source of Wrapper.pm and looking at "envsave" there at the top).
-Is this the case?  --Glenn
-
-> That seems likely. You can edit Wrapper.pm and add `SVN_SSH` to the
-> `@envsave` list and rebuild your wrappers to test it. --[[Joey]]