From 313a0285e5eb18867b3781dbad1222e2d02675e2 Mon Sep 17 00:00:00 2001 From: jkniiv Date: Sat, 1 Jun 2024 22:11:32 +0000 Subject: [PATCH] a small clarification --- ...nnex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn b/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn index c67097ff66..df2d612a32 100644 --- a/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn +++ b/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn @@ -1,8 +1,8 @@ ### Please describe the problem. -The new git-remote-annex functionality doesn't appear to work due to not being able -to delete temporary files (problem with thawing content, perhaps). Somehow, the -temp files (e.g. GITBUNDLE objects) seem to have their readonly attribute stubbornly +The new git-remote-annex functionality doesn't appear to work on Windows due to git-annex +not being able to delete temporary files (problem with thawing content, perhaps). Somehow, the +temp files (e.g. GITBUNDLE objects) seem to have their read-only attribute stubbornly set (from git-annex's view). On a happier note, git-remote-annex works just fine on WSL2 operating annexes and