From 9d9e3d6d1a1fc03566fbc77c0c1d474a4b1bdbff Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 13 Sep 2022 15:07:58 -0400 Subject: [PATCH] comment --- ...nt_2_df6e152f1291c3dc1ba2b1b03b18083e._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/tips/Using_git-annex_on_NTFS_with_WSL1/comment_2_df6e152f1291c3dc1ba2b1b03b18083e._comment diff --git a/doc/tips/Using_git-annex_on_NTFS_with_WSL1/comment_2_df6e152f1291c3dc1ba2b1b03b18083e._comment b/doc/tips/Using_git-annex_on_NTFS_with_WSL1/comment_2_df6e152f1291c3dc1ba2b1b03b18083e._comment new file mode 100644 index 0000000000..78f67b141d --- /dev/null +++ b/doc/tips/Using_git-annex_on_NTFS_with_WSL1/comment_2_df6e152f1291c3dc1ba2b1b03b18083e._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""Re: Using git-annex on NTFS with WSL2""" + date="2022-09-13T19:00:44Z" + content=""" +I have not had the chance to try WSL2, but I think that git-annex should +work on it more or less without any issues or anything special. + +When the repository is on a filesystem that either does not support +symlinks, or where you will also want to be able to access files in the +repository from Windows outside of WSL2 without the complication of +symlinks, it does make sense to avoid locked files. +`git-annex adjust --unlock` is a good way to make that be the +case for all the files in the repository. +"""]] -- 2.30.2