diff --git a/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume.mdwn b/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume.mdwn
index fd5b15b519..3f4fe29d86 100644
--- a/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume.mdwn
+++ b/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume.mdwn
@@ -29,6 +29,4 @@ I let it try to resume for a very long time (about a day) and it did nothing.
 
 This is a fairly large repository which was only just cloned and with all data transferred (`git clone` and `git annex get .` worked fine).
 
-
-
-
+> [[closing|done]] per my comment --[[Joey]]
diff --git a/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume/comment_1_2aa8d50cef4f85d958371e2177f87d3a._comment b/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume/comment_1_2aa8d50cef4f85d958371e2177f87d3a._comment
new file mode 100644
index 0000000000..a1226cd2c3
--- /dev/null
+++ b/doc/bugs/__96__git_annex_direct__96___failed_and_will_not_resume/comment_1_2aa8d50cef4f85d958371e2177f87d3a._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-05-04T17:01:56Z"
+ content="""
+git-annex no longer supports direct mode in current versions,
+so whatever code might have caused that behavior is removed.
+
+The signal 11 is, however, suprising. If a current version of git-annex
+segfaults, it would be worth filing a bug report and chasing that down,
+although only after you test your machine's memory for problems that might
+lead to a sefault.
+"""]]