From 14607a10f92c8859fc6c4b28c59b228c131f9c87 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 30 Oct 2011 12:48:34 -0400 Subject: bug responses (Yes, I'm still alive) --- ..._entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc/bugs/several_entries_in_docs__47__bugs_contain_colons_in_the_filename.mdwn') 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 c7cf8e320..03f478778 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 +1,9 @@ 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? + +> Well, this is a difficult thing. Ikiwiki has a configuration setting to +> prevent it writing filenames with colons, but for backwards compatability +> that is not enabled by default. Also nothing would stop people from +> making commits that added filenames with colons even if it were disabled +> 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]] -- cgit v1.2.3