summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus <Jimmy@web>2011-03-27 12:58:15 +0000
committerGravatar admin <admin@branchable.com>2011-03-27 12:58:15 +0000
commitca5a6f4f42237136550347539f7d51376beef997 (patch)
tree7346880e1c9f928f1242e691c50cad08e283614c
parent07d15ab2eae88059f2a90e1b389e5ce34deeafe6 (diff)
-rw-r--r--doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn b/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
new file mode 100644
index 000000000..9320b30a9
--- /dev/null
+++ b/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
@@ -0,0 +1,13 @@
+Currently the hashed directories in .git-annex allow for upper and lower case directory names... on linux (or any case sensitive filesystem) the directory names such as 'Gg' and 'GG' are different and unique. However on systems like OSX (and probably windows if it is ever supported) the directory names 'Gg' is the same as 'GG'
+
+In one of the annex'd repos that I have this has occured...
+
+<pre>
+$ git add -i
+ staged unstaged path
+ 1: unchanged +1/-1 .git-annex/GM/GV/WORM-s183630166-m1301072171--somefile.log
+ 2: unchanged +1/-1 .git-annex/Gm/GV/WORM-s183630166-m1301072171--somefile.log
+</pre>
+
+
+this has somewhat confused git when it tries to stage/merge files, I didn't notice this at first, but it is definately a problem for someone using case insensitive filesystems like the default OSX HFS+ formats or vfat/fat32.