aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/several_entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/bugs/several_entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn b/doc/bugs/several_entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn
index 03f478778..62a8c57a1 100644
--- a/doc/bugs/several_entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn
+++ b/doc/bugs/several_entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn
@@ -1,4 +1,4 @@
-I just tried to clone the git repo onto a windows machine to test things out a bit and it turns out i cannot even successfully checkout the code because of those colons. Would a patch changing those to underscores be accepted?
+I just tried to clone the git repo onto a windows machine to test things out a bit and it turns out i cannot even successfully checkout the code because of those colons. Would a patch changing those to underscores be accepted? --Mithaldu
> Well, this is a difficult thing. Ikiwiki has a configuration setting to
> prevent it writing filenames with colons, but for backwards compatability
@@ -7,3 +7,5 @@ I just tried to clone the git repo onto a windows machine to test things out a b
> in ikiwiki. I don't know that trying to work around obscure limitations
> in OSs that I've never heard of ikiwiki being used on is worth the bother
> TBH, but have not really made up my mind. --[[Joey]]
+
+>> I'm not trying to run it there. Ikiwiki is way too friggin' weird to try that. I just want to be able to check out the main repo so i can work in a native editor. Right now your core repository is downright hostile to cross-platform development in any way, shape or form. (Just plain splitting the docs from the code would work too.) --Mithaldu