diff --git a/doc/bugs/Guard_against_previously_annexed_dotfiles_being_converted_to_git_files__63__/comment_1_e9f5fdf1078c87718fb6ca2559323b1e._comment b/doc/bugs/Guard_against_previously_annexed_dotfiles_being_converted_to_git_files__63__/comment_1_e9f5fdf1078c87718fb6ca2559323b1e._comment
new file mode 100644
index 0000000000..ec0e3b6391
--- /dev/null
+++ b/doc/bugs/Guard_against_previously_annexed_dotfiles_being_converted_to_git_files__63__/comment_1_e9f5fdf1078c87718fb6ca2559323b1e._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-03-09T17:00:38Z"
+ content="""
+This looks like a serious regression in 8.x. It is not an intentional part
+of the annex.dotfiles change. I have confirmed the last 7.x release did not
+have the behavior.
+
+(Notice that annex.dotfiles is not used in the repo where the problem
+occurs. The regression was probably introduced by the annex.dotfiles
+changes, but the dotfile could just as well have been added by git-annex v5
+with git-annex add --include-dotfiles and the result committed to git would
+be the same.)
+
+A simpler test case is to unlock the dotfile in the first repo, then
+all that needs to be run in its clone is `git annex get`.
+"""]]