comment

diff --git a/doc/forum/Cannot_get_unlocked_file_contents/comment_3_be1f3ec26c14ca9adc9d8f24ea096976._comment b/doc/forum/Cannot_get_unlocked_file_contents/comment_3_be1f3ec26c14ca9adc9d8f24ea096976._comment
new file mode 100644 (file)
index 0000000..7a02c4e
--- /dev/null
+++ b/doc/forum/Cannot_get_unlocked_file_contents/comment_3_be1f3ec26c14ca9adc9d8f24ea096976._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2020-10-12T20:10:38Z"
+ content="""
+Like I said, committing the hash link, for an unlocked file, is
+perfectly normal. And will not result in this behavior.
+
+You need to show command output of commands like git-annex get, git-annex
+whereis, git-annex fsck for us to understand what the actual problem is.
+"""]]