diff --git a/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_15_feb18c6e8be6d4cf3c1730f451531787._comment b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_15_feb18c6e8be6d4cf3c1730f451531787._comment
new file mode 100644
index 0000000000..fc9667ee0c
--- /dev/null
+++ b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_15_feb18c6e8be6d4cf3c1730f451531787._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="clarifying preferred content expressions"
+ date="2021-05-30T19:40:50Z"
+ content="""
+Thanks Joey for clarifying.  \"Preferred content only relates to the currently checked out branch\" -- what about repos with no \"currently checked out branch\", e.g. bare repos or special remotes, or those with more than one checked out branch (using [[git-worktree|tips/Using_git-worktree_with_annex]])?   I had thought that e.g. setting the required content setting of an S3 special remote to `anything` would ensure that it gets a copy of every file ever annexed, but sounds like that might not be true.
+"""]]