comment
authorJoey Hess <joeyh@joeyh.name>
Wed, 1 Mar 2023 19:58:47 +0000 (15:58 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 1 Mar 2023 19:58:47 +0000 (15:58 -0400)
doc/bugs/testremote_is_not_honoring_--backend/comment_6_7a9cb82671ff8a459886a84e66cb2417._comment [new file with mode: 0644]

diff --git a/doc/bugs/testremote_is_not_honoring_--backend/comment_6_7a9cb82671ff8a459886a84e66cb2417._comment b/doc/bugs/testremote_is_not_honoring_--backend/comment_6_7a9cb82671ff8a459886a84e66cb2417._comment
new file mode 100644 (file)
index 0000000..d6d62a7
--- /dev/null
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 6"""
+ date="2023-03-01T19:56:27Z"
+ content="""
+In [[!commit 54ad1b4cfb1c8302f1b862cb2699ab9351e3eb5b]] I fully worked
+around this class of problems with unix-compat.
+
+I think it's reasonably likely that every access of a file in git-annex
+on Windows now goes through UNC-style normalization, allowing long
+filenames to be used. Assuming that everything in ghc base does it, which I
+think it does.
+
+So good chance this is fixed now..
+"""]]