diff --git a/doc/forum/sync_--content__44___fatal_is_outside_repository_errors/comment_10_d4a649874ee9c9e6a4c0252700607713._comment b/doc/forum/sync_--content__44___fatal_is_outside_repository_errors/comment_10_d4a649874ee9c9e6a4c0252700607713._comment
new file mode 100644
index 0000000000..7e936266bc
--- /dev/null
+++ b/doc/forum/sync_--content__44___fatal_is_outside_repository_errors/comment_10_d4a649874ee9c9e6a4c0252700607713._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 9"""
+ date="2018-07-17T19:16:23Z"
+ content="""
+Hmm, maybe.
+
+It's very difficult to say without enough of a transcript to have any idea
+at what point in the `git annex sync` it was failing. If it failed in the
+"commit" part, then yes, it could be git commit running the smudge/clean filter
+and the worktree path problem affecting it.
+"""]]