From cf649b5753623ec14378deaf7e830cabffc8070d Mon Sep 17 00:00:00 2001 From: falsifian Date: Wed, 2 Dec 2020 16:52:10 +0000 Subject: [PATCH 1/6] Added a comment --- .../comment_2_f8435628336b472107b478fe11628186._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/git-annex_sometimes_messes_up___126____47__.git-credentials/comment_2_f8435628336b472107b478fe11628186._comment diff --git a/doc/bugs/git-annex_sometimes_messes_up___126____47__.git-credentials/comment_2_f8435628336b472107b478fe11628186._comment b/doc/bugs/git-annex_sometimes_messes_up___126____47__.git-credentials/comment_2_f8435628336b472107b478fe11628186._comment new file mode 100644 index 0000000000..98c4a25b50 --- /dev/null +++ b/doc/bugs/git-annex_sometimes_messes_up___126____47__.git-credentials/comment_2_f8435628336b472107b478fe11628186._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="falsifian" + avatar="http://cdn.libravatar.org/avatar/59c3c23c500d20d83ecb9d1f149be9ae" + subject="comment 2" + date="2020-12-02T16:52:10Z" + content=""" +Thanks for the info. So I guess some combination of `git credential fill` and `git credential approve` is causing this. If I have more time I'll fiddle with those commands. +"""]] From c9b33c553d8391bea9c70156d194bc690008b5fc Mon Sep 17 00:00:00 2001 From: "rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" Date: Thu, 3 Dec 2020 01:43:00 +0000 Subject: [PATCH 2/6] Added a comment --- ...mment_15_4be14df022612d6301442b3210a17d0a._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/tips/unlocked_files/comment_15_4be14df022612d6301442b3210a17d0a._comment diff --git a/doc/tips/unlocked_files/comment_15_4be14df022612d6301442b3210a17d0a._comment b/doc/tips/unlocked_files/comment_15_4be14df022612d6301442b3210a17d0a._comment new file mode 100644 index 0000000000..8b868d8d8c --- /dev/null +++ b/doc/tips/unlocked_files/comment_15_4be14df022612d6301442b3210a17d0a._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" + nickname="rshalaev" + avatar="http://cdn.libravatar.org/avatar/d7f181d338cbcef7418faa01f0441e86" + subject="comment 15" + date="2020-12-03T01:43:00Z" + content=""" +Is where any way to make Git Annex use Windows 10 NTFS hardlinks in the working tree? + +Looking to conserve disk-space while still being able to browse and view files content. Currently Git Annex is doubling the ammount of disk space. +"""]] From 08c6ffa117ec3992711f6efe4b80431518d297fa Mon Sep 17 00:00:00 2001 From: "rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" Date: Thu, 3 Dec 2020 01:43:20 +0000 Subject: [PATCH 3/6] Added a comment --- ...mment_16_494a50df606af18adfea06bb26c3bbdb._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment diff --git a/doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment b/doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment new file mode 100644 index 0000000000..5def4d982f --- /dev/null +++ b/doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" + nickname="rshalaev" + avatar="http://cdn.libravatar.org/avatar/d7f181d338cbcef7418faa01f0441e86" + subject="comment 16" + date="2020-12-03T01:43:20Z" + content=""" +Is where any way to make Git Annex use Windows 10 NTFS hardlinks in the working tree? + +Looking to conserve disk-space while still being able to browse and view files content. Currently Git Annex is doubling the ammount of disk space. +"""]] From 894d7c07aa193b0a107a30ee18cb10b19d5e7fa9 Mon Sep 17 00:00:00 2001 From: "rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" Date: Thu, 3 Dec 2020 01:44:01 +0000 Subject: [PATCH 4/6] removed --- ...mment_16_494a50df606af18adfea06bb26c3bbdb._comment | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment diff --git a/doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment b/doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment deleted file mode 100644 index 5def4d982f..0000000000 --- a/doc/tips/unlocked_files/comment_16_494a50df606af18adfea06bb26c3bbdb._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" - nickname="rshalaev" - avatar="http://cdn.libravatar.org/avatar/d7f181d338cbcef7418faa01f0441e86" - subject="comment 16" - date="2020-12-03T01:43:20Z" - content=""" -Is where any way to make Git Annex use Windows 10 NTFS hardlinks in the working tree? - -Looking to conserve disk-space while still being able to browse and view files content. Currently Git Annex is doubling the ammount of disk space. -"""]] From b0320b11086386b19bfb820e4d1a13a2c8588ce9 Mon Sep 17 00:00:00 2001 From: Lukey Date: Thu, 3 Dec 2020 07:38:31 +0000 Subject: [PATCH 5/6] Added a comment --- .../comment_16_61121c6b95e1310df8132aca13924b88._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/tips/unlocked_files/comment_16_61121c6b95e1310df8132aca13924b88._comment diff --git a/doc/tips/unlocked_files/comment_16_61121c6b95e1310df8132aca13924b88._comment b/doc/tips/unlocked_files/comment_16_61121c6b95e1310df8132aca13924b88._comment new file mode 100644 index 0000000000..e5496b4244 --- /dev/null +++ b/doc/tips/unlocked_files/comment_16_61121c6b95e1310df8132aca13924b88._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 16" + date="2020-12-03T07:38:30Z" + content=""" +Yes, as the page above explains, `git config annex.thin true` and then `git annex fix` +"""]] From c82048ba79c2722d61b7a3ecbf3408d77bb9fa0e Mon Sep 17 00:00:00 2001 From: "rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" Date: Thu, 3 Dec 2020 11:43:08 +0000 Subject: [PATCH 6/6] Added a comment: Windows 10 NTFS hardlinks not working --- ..._15c6f8db289812e76859b21d158b1b2e._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/tips/unlocked_files/comment_17_15c6f8db289812e76859b21d158b1b2e._comment diff --git a/doc/tips/unlocked_files/comment_17_15c6f8db289812e76859b21d158b1b2e._comment b/doc/tips/unlocked_files/comment_17_15c6f8db289812e76859b21d158b1b2e._comment new file mode 100644 index 0000000000..882cdd1247 --- /dev/null +++ b/doc/tips/unlocked_files/comment_17_15c6f8db289812e76859b21d158b1b2e._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="rshalaev@3e2130a1e3cb0aaff7dd80aba7548ad9be0ea2d4" + nickname="rshalaev" + avatar="http://cdn.libravatar.org/avatar/d7f181d338cbcef7418faa01f0441e86" + subject="Windows 10 NTFS hardlinks not working" + date="2020-12-03T11:43:07Z" + content=""" +Lukey - I tried git config annex.thin true and then git annex fix + +Doing it on Windows NTFS drive did not create hard-links. I've followed the instructions. Could not get it to work. Always got copies of files instead of hardlinks. + +From: -- Joey Hess Mon, 18 Apr 2016 18:33:52 -0400 +git-annex (6.20160412) Changelog + * annex.thin and annex.hardlink are now supported on Windows. + +Based on Joey change log - hard links should work on NTFS. According to my obesrvation and a report from colin.brosseau above (titles \"NTFS Make it clear that it'll not work with annex.thin\") it does not work. + +Can anyone confirm if git annex can creates NTFS hardlinks? I can file a bug report if needed. + +Thanks! +"""]]