From 41f6442b52180ac14f3429c270b376fd340a9690 Mon Sep 17 00:00:00 2001 From: Nikodemus Siivola Date: Fri, 9 Feb 2024 11:59:57 +0200 Subject: [PATCH] no colons in filenames: issues with Git, especially on Windows Since Git uses colons to separate pathnames from tree ids in several commands, a filename with a colon in it can create additional confusion when scripting Git. Additionally, NTFS filename protection rules on Git on Windows are overly strict, and prevent checkouts when there are any colons in filenames. (Two consequtive colons is what would create an issue.) --- data/o_c_hemisphere/{Mixer:Balance.html => Mixer-Balance.html} | 0 data/o_c_hemisphere/module.xml | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename data/o_c_hemisphere/{Mixer:Balance.html => Mixer-Balance.html} (100%) diff --git a/data/o_c_hemisphere/Mixer:Balance.html b/data/o_c_hemisphere/Mixer-Balance.html similarity index 100% rename from data/o_c_hemisphere/Mixer:Balance.html rename to data/o_c_hemisphere/Mixer-Balance.html diff --git a/data/o_c_hemisphere/module.xml b/data/o_c_hemisphere/module.xml index 301b7f4..6072fb3 100644 --- a/data/o_c_hemisphere/module.xml +++ b/data/o_c_hemisphere/module.xml @@ -204,7 +204,7 @@ - + utility