diff --git a/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_16_578671b5758d78180d9dae273c4475aa._comment b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_16_578671b5758d78180d9dae273c4475aa._comment
new file mode 100644
index 0000000000..63cb8f4047
--- /dev/null
+++ b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_16_578671b5758d78180d9dae273c4475aa._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 16"""
+ date="2021-05-31T21:50:35Z"
+ content="""
+By "currently checked out branch", I meant in the repository where
+git-annex is running. It might be copying to a special remote or whatever,
+but the filename matched by include= or exclude= in a preferred content
+expression comes from the branch it's run in.
+
+When run in a bare git repo (or with --all), include= and exclude= are
+documented not to match.
+"""]]
diff --git a/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_15_06641815750038a0ed908d929868c1c3._comment b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_15_06641815750038a0ed908d929868c1c3._comment
new file mode 100644
index 0000000000..0488fad8e1
--- /dev/null
+++ b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_15_06641815750038a0ed908d929868c1c3._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 15"""
+ date="2021-05-31T21:49:35Z"
+ content="""
+[[bugs/indeterminite_preferred_content_state_for_duplicated_file]]
+"""]]