comment
authorJoey Hess <joeyh@joeyh.name>
Mon, 19 Oct 2020 17:04:03 +0000 (13:04 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 19 Oct 2020 17:04:03 +0000 (13:04 -0400)
doc/bugs/old__40__er__41___cp_from_coreutils_lacks_--reflink/comment_4_c2d4485b2a49ada5ab5266e30df91b0b._comment [new file with mode: 0644]

diff --git a/doc/bugs/old__40__er__41___cp_from_coreutils_lacks_--reflink/comment_4_c2d4485b2a49ada5ab5266e30df91b0b._comment b/doc/bugs/old__40__er__41___cp_from_coreutils_lacks_--reflink/comment_4_c2d4485b2a49ada5ab5266e30df91b0b._comment
new file mode 100644 (file)
index 0000000..da50534
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2020-10-19T16:39:28Z"
+ content="""
+I installed git for windows in a fresh windows 10
+VM. Then I installed git-annex from the git-annex for windows installer. 
+Then I ran git-annex add, which ran cp --reflink successfully.
+
+But you didn't say how you installed git-annex on windows, did you?
+I guess, since you're building it yourself, you put it into path somewhere
+else. So it seems to me, it's the up to you to make its path include the
+same cp you built it against. 
+
+Or just build the windows installer too, and install your git-annex build
+using that.
+"""]]