response
authorJoey Hess <joeyh@joeyh.name>
Mon, 9 Mar 2020 19:09:15 +0000 (15:09 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 9 Mar 2020 19:09:15 +0000 (15:09 -0400)
doc/bugs/__34__Illegal_instruction__34___when_running_certain_tests_on_AMD_Phenom_II/comment_6_c87be8241a5facb94cb9146ebb31a7de._comment [new file with mode: 0644]

diff --git a/doc/bugs/__34__Illegal_instruction__34___when_running_certain_tests_on_AMD_Phenom_II/comment_6_c87be8241a5facb94cb9146ebb31a7de._comment b/doc/bugs/__34__Illegal_instruction__34___when_running_certain_tests_on_AMD_Phenom_II/comment_6_c87be8241a5facb94cb9146ebb31a7de._comment
new file mode 100644 (file)
index 0000000..411ab6b
--- /dev/null
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 6"""
+ date="2020-03-09T19:00:35Z"
+ content="""
+git-annex does not use blake2 by default. If someone has configured it to
+use blake2 (probably because they want the speed) and added some files to 
+a repo, it will then use blake2 to hash those files going forward.
+
+So, in balance, it seems better to disable the unsafe optimisation,
+and have it be a little bit slower, than not work on some machines.
+
+Thanks for fileing the issue on cryptonite. I don't see anything further to
+be done in git-annex, so I'll close this bug now.
+"""]]