From 83a378685134dde56b66e79101a4b6cd93e82182 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 1 Mar 2023 15:58:47 -0400 Subject: [PATCH] comment --- ...nt_6_7a9cb82671ff8a459886a84e66cb2417._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/testremote_is_not_honoring_--backend/comment_6_7a9cb82671ff8a459886a84e66cb2417._comment 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 index 0000000000..d6d62a7837 --- /dev/null +++ b/doc/bugs/testremote_is_not_honoring_--backend/comment_6_7a9cb82671ff8a459886a84e66cb2417._comment @@ -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.. +"""]] -- 2.30.2