try

[git.ikiwiki.info.git] / doc / about_rcs_backends.mdwn

diff --git a/doc/about_rcs_backends.mdwn b/doc/about_rcs_backends.mdwn
index d277d97bcac8c5e1e3936d11103b3e341db12709..2f0fef0d3ebf35fa90b0e7f053d04c1f3e046e8b 100644 (file)
--- a/doc/about_rcs_backends.mdwn
+++ b/doc/about_rcs_backends.mdwn
@@ -2,8 +2,6 @@ A few bits about the RCS backends
 
 [[toc ]]
 
 
 [[toc ]]
 

-[[foo]]
-

 ## Terminology
 
 ``web-edit'' means that a page is edited by using the web (CGI) interface
 ## Terminology
 
 ``web-edit'' means that a page is edited by using the web (CGI) interface


@@ -38,7 +36,7 @@ W "belongs" to ikiwiki and should not be edited directly.
 
 Support for using darcs as a backend is being worked on by [Thomas
 Schwinge](mailto:tschwinge@gnu.org), although development is on hold curretly.
 
 Support for using darcs as a backend is being worked on by [Thomas
 Schwinge](mailto:tschwinge@gnu.org), although development is on hold curretly.

-There is a patch in the [[patchqueue]].
+There is a patch in [[todo/darcs]].

 
 ### How will it work internally?
 
 
 ### How will it work internally?
 


@@ -116,7 +114,7 @@ towards transmitting changes with standalone patch bundles (often by email) as d
 >> IMHO it comes down to whatever works well for a given RCS. Seems like
 >> the darcs approach _could_ be done with most any distributed system, but
 >> it might be overkill for some (or all?) While there is the incomplete darcs
 >> IMHO it comes down to whatever works well for a given RCS. Seems like
 >> the darcs approach _could_ be done with most any distributed system, but
 >> it might be overkill for some (or all?) While there is the incomplete darcs

->> plugin in the [[patchqueue]], if you submit one that's complete, I will
+>> plugin in [[todo/darcs]], if you submit one that's complete, I will

 >> probably accept it into ikiwiki.. --[[Joey]]
 
 ## [[Git]]
 >> probably accept it into ikiwiki.. --[[Joey]]
 
 ## [[Git]]