diff --git a/doc/bugs/v6_hardlinking_is_not_stable_across_lock__47__unlock_or_cloning/comment_2_6c6ed937660b6f19829362c2c2cb4991._comment b/doc/bugs/v6_hardlinking_is_not_stable_across_lock__47__unlock_or_cloning/comment_2_6c6ed937660b6f19829362c2c2cb4991._comment
new file mode 100644
index 0000000000..dbe7e8921e
--- /dev/null
+++ b/doc/bugs/v6_hardlinking_is_not_stable_across_lock__47__unlock_or_cloning/comment_2_6c6ed937660b6f19829362c2c2cb4991._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2018-10-18T19:45:15Z"
+ content="""
+When two files have the same content, annex.thin will only make one of them
+be a hard link to the annex object. The other file will have its own
+redundant copy of the content. This is the only way to prevent an edit to
+one file immediatly changing the other file, which would be very surprising
+behavior.
+
+When the file in git has the executable bit set, annex.thin is not honored
+for that file either. That's a lot simpler than juggling permissions
+around.
+
+Does that explain everything you're seeing, or is there still a bug buried
+in that transcript? I have not had time to read the whole thing.
+"""]]