Remove question about subversion. The details are slightly hairy, suffice

to say that it makes sense for ikiwiki to know where the svn repo is, and
not extract this info from the WC every time.

diff --git a/doc/about_rcs_backends.mdwn b/doc/about_rcs_backends.mdwn
index 079dd1576e5731e310a7c858b947bf7e5b4a651f..7af4a952e1f770fa3dd6ffb1f19f95eb13e67e4b 100644 (file)
--- a/doc/about_rcs_backends.mdwn
+++ b/doc/about_rcs_backends.mdwn
@@ -184,13 +184,11 @@ There is a patch that needs a bit of work linked to from [[todo/rcs]].
 
 ## [Monotone](http://monotone.ca/)
 
 
 ## [Monotone](http://monotone.ca/)
 

-There is a patch in [[bugs/Monotone_rcs_support]].  It works, but its conflict handling is a little ugly.
-

 In normal use, monotone has a local database as well as a workspace/working copy.
 In ikiwiki terms, the local database takes the role of the master repository, and
 the srcdir is the workspace.  As all monotone workspaces point to a default
 database, there is no need to tell ikiwiki explicitly about the "master" database.  It
 In normal use, monotone has a local database as well as a workspace/working copy.
 In ikiwiki terms, the local database takes the role of the master repository, and
 the srcdir is the workspace.  As all monotone workspaces point to a default
 database, there is no need to tell ikiwiki explicitly about the "master" database.  It

-will know.  (BTW - this is also true of subversion.  It might be possible to simplify the svn config?)
+will know.

 
 The patch currently supports normal committing and getting the history of the page.
 To understand the parallel commit approach, you need to understand monotone's
 
 The patch currently supports normal committing and getting the history of the page.
 To understand the parallel commit approach, you need to understand monotone's