comment

diff --git a/doc/bugs/git-annex_get__58___createDirectory__58___does_not_exist/comment_5_f2a25cca5d72ce1dcecf36c2780abec2._comment b/doc/bugs/git-annex_get__58___createDirectory__58___does_not_exist/comment_5_f2a25cca5d72ce1dcecf36c2780abec2._comment
new file mode 100644 (file)
index 0000000..c2cf84b
--- /dev/null
+++ b/doc/bugs/git-annex_get__58___createDirectory__58___does_not_exist/comment_5_f2a25cca5d72ce1dcecf36c2780abec2._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2021-01-18T17:29:12Z"
+ content="""
+I can't see how git-annex can work around this, unless someone finds an
+explanation for the OS's behavior.
+
+I think you've clearly shown it's not a git-annex bug, since other mkdir()
+calls behave the same way. And that seems to point squarely at an OS bug.
+
+(Unless .git/annex was itself a dangling symlink, then ls would be able to
+list it, but mkdir would fail like that.)
+"""]]