From: Joey Hess Date: Mon, 18 Jan 2021 17:40:31 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~98^2~196 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=c0ffb5c2c4250a381b6771fae9a4077ad47230c5;p=git-annex.git 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 index 0000000000..c2cf84be00 --- /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.) +"""]]