From c1229f959adc5da1731781fcdd9a2d1cd3afe8d4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 27 Oct 2021 14:40:02 -0400 Subject: [PATCH] comment --- ..._ab64e43330e466482f30487b8bd13bbf._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/WSL1__58___git-annex-add_fails_in_DrvFs_filesystem/comment_4_ab64e43330e466482f30487b8bd13bbf._comment diff --git a/doc/bugs/WSL1__58___git-annex-add_fails_in_DrvFs_filesystem/comment_4_ab64e43330e466482f30487b8bd13bbf._comment b/doc/bugs/WSL1__58___git-annex-add_fails_in_DrvFs_filesystem/comment_4_ab64e43330e466482f30487b8bd13bbf._comment new file mode 100644 index 0000000000..210582f5f7 --- /dev/null +++ b/doc/bugs/WSL1__58___git-annex-add_fails_in_DrvFs_filesystem/comment_4_ab64e43330e466482f30487b8bd13bbf._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2021-10-27T18:19:58Z" + content=""" +Interesting, thanks for that analysis. + +I don't like the prospect of adding hacks to git-annex on linux to deal +with infelicities of WSL1. WSL should emulate linux well, and to the +extent it does not, that seems Microsoft's problem, not mine. + +However, I wonder what that analysis implies about the other linked bugs +with similar error messages, which are on OSX and (probably) Linux. + +What could be done to detect this drvfs problem is to add this case to the +probing that's done for crippled filesystems. Then it would take the +nohardlink path. + +But drvfs is used for /mnt/c/ etc, so that would make most all repos on WSL1 be +treated as in a crippled filesystem, using unlocked adjusted branches, etc. + +Also, I seem to remember using git-annex in WSL1 in /mnt/c/ and git-annex +add presumably working. So I wonder what has changed. +"""]]