summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2010-06-08 14:50:24 -0400
committerJoey Hess <joey@kitenet.net>2010-06-08 14:50:24 -0400
commit868f5a94bfdf03ccb720d561cf99185d7182cb77 (patch)
tree7015d2dae829181ca8a8e5b0974882a70fa1796d
parentc911b4b998992a69b5eea167658fb00c52a064a1 (diff)
response
-rw-r--r--doc/bugs/tag_plugin:_autotag_vs._staged_changes.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/tag_plugin:_autotag_vs._staged_changes.mdwn b/doc/bugs/tag_plugin:_autotag_vs._staged_changes.mdwn
index 8678249bb..2419cf75f 100644
--- a/doc/bugs/tag_plugin:_autotag_vs._staged_changes.mdwn
+++ b/doc/bugs/tag_plugin:_autotag_vs._staged_changes.mdwn
@@ -1,3 +1,14 @@
The autotag functionality of the tag plugin committed (when doing its
first commit) all changes that have been staged (in Git). I suggest it
should be restricted to the specific file only. --[[tschwinge]]
+
+> This is not specific to the tag plugin. Same can happen
+> if you rename a file, or post a comment, or remove a file
+> via web interface. All of these use `rcs_commit_staged`.
+>
+> This is why ikiwiki is supposed to have a checkout of
+> the repository that it uses for its own purposes, and nobody else
+> should mess with. There are various notes about that being needed here
+> and there; you're free to not give ikiwiki its own repo, but you have to
+> be aware that it can fight with you if you're making changes to the same
+> repo. [[done]] --[[Joey]]