aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2011-01-08 11:57:35 -0400
committerJoey Hess <joey@kitenet.net>2011-01-08 11:57:35 -0400
commite380cd0c461a78de95911d5f5925ceba24b3f8cd (patch)
treea842772c71ee0d32b0efc4e5e9dfa43cb17efc6b
parentca5fbc7c204d188f0e05686d21de851fbc47a5b4 (diff)
downloadikiwiki-e380cd0c461a78de95911d5f5925ceba24b3f8cd.tar
ikiwiki-e380cd0c461a78de95911d5f5925ceba24b3f8cd.tar.gz
Revert "Correct doc/patch.mdwn documentation: tag -> link."
This reverts commit ca5fbc7c204d188f0e05686d21de851fbc47a5b4. It's perfectly ok, and common practice to tag things patch.
-rw-r--r--doc/patch.mdwn3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/patch.mdwn b/doc/patch.mdwn
index a1c304c58..b570d995c 100644
--- a/doc/patch.mdwn
+++ b/doc/patch.mdwn
@@ -2,8 +2,7 @@ Since we have enough people working on ikiwiki to be dangerous, or at least
to duplicate work without coordination, here's a queue of suggested patches.
If you post a patch to the [[todo]] or [[bugs]] list, or elsewhere,
-once it's ready to be applied, add a link to 'patch' so it will show
-up here.
+once it's ready to be applied, add a 'patch' tag so it will show up here.
If your patch is non-trivial and might need several iterations to get
right, please consider publishing a [[git]] branch.