diff --git a/doc/forum/How_to_sync_without_enumerating_files__63__/comment_1_ad78c67ae1bb4dc8ed800779c0298158._comment b/doc/forum/How_to_sync_without_enumerating_files__63__/comment_1_ad78c67ae1bb4dc8ed800779c0298158._comment
new file mode 100644
index 0000000000..f79b3592fc
--- /dev/null
+++ b/doc/forum/How_to_sync_without_enumerating_files__63__/comment_1_ad78c67ae1bb4dc8ed800779c0298158._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-10-31T17:15:33Z"
+ content="""
+Well, `git annex sync` does not itself run `git status`. 
+
+Try running git-annex with the --debug option, it will say what git
+commands it runs, and that should help find out which git command is
+complaining.
+
+My guess is it's `git commit`, which  is probably getting the status
+unncessarily for a commit message template, despite a commit message
+being specified. If so, `git annex sync --no-commit` would avoid
+that.
+"""]]