diff --git a/doc/bugs/__96__sync_-C__96___takes_longer_to_get_file_than___96__get__96__/comment_12_b0132b0f846e4882a5511b53694a1fa2._comment b/doc/bugs/__96__sync_-C__96___takes_longer_to_get_file_than___96__get__96__/comment_12_b0132b0f846e4882a5511b53694a1fa2._comment
new file mode 100644
index 0000000000..d5a71432b0
--- /dev/null
+++ b/doc/bugs/__96__sync_-C__96___takes_longer_to_get_file_than___96__get__96__/comment_12_b0132b0f846e4882a5511b53694a1fa2._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="jkniiv"
+ avatar="http://cdn.libravatar.org/avatar/05fd8b33af7183342153e8013aa3713d"
+ subject="comment 12"
+ date="2021-10-02T19:58:17Z"
+ content="""
+Thanks, Joey! 💐 Well done. :)
+"""]]
diff --git a/doc/design/external_special_remote_protocol/comment_47_9d48c85b896f738323dec28c1955ee22._comment b/doc/design/external_special_remote_protocol/comment_47_9d48c85b896f738323dec28c1955ee22._comment
new file mode 100644
index 0000000000..7f55ded02d
--- /dev/null
+++ b/doc/design/external_special_remote_protocol/comment_47_9d48c85b896f738323dec28c1955ee22._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="alex@f04d0d3c452a2a99b27ccc93c1543bee4a1bf5be"
+ nickname="alex"
+ avatar="http://cdn.libravatar.org/avatar/9d97e9bcb1cf7680309e37cd69fab408"
+ subject="Resuming an interrupted download"
+ date="2021-10-01T23:27:31Z"
+ content="""
+It would be helpful to allow special remotes to take advantage of git annex's ability to resume interrupted downloads for large files, especially on slow/unreliable connections. One way to implement this would be to allow the special remote to send a message asking git-annex what offset it intends to read at, then write a sparse file with only the needed data. I notice the `testremote` suite includes tests for resuming downloads at an offset, so it is possible no other changes would be needed.
+
+Sparse files could be avoided by allowing the special remote to send a command indicating the offset at which the target file starts.
+
+Does that sound like a reasonable design?
+"""]]
diff --git a/doc/forum/config_to_make_git_annex_sync_only_sync_metadata__63__.mdwn b/doc/forum/config_to_make_git_annex_sync_only_sync_metadata__63__.mdwn
new file mode 100644
index 0000000000..174f4f35d2
--- /dev/null
+++ b/doc/forum/config_to_make_git_annex_sync_only_sync_metadata__63__.mdwn
@@ -0,0 +1,7 @@
+I would like `git annex sync` to only sync `git-annex`'s bookkeeping metadata, and *not* my master branch or file content.
+
+I tried setting `annex.synconlyannex = true` (in `~/.gitconfig`), and was surprised to find that although that disables syncing of my master branch, it *enables* syncing of content.
+
+I can add `--no-content` on the command line, but I'd rather not type that every time. Is there a way to do it purely through `~/.gitconfig`? (Maybe consider it as a feature request?)
+
+(Motivation: I find it jarring when git annex creates git commits on my own branches without asking me. I already set `annex.autocommit = false`, but `git annex sync` will still make merge commits unless I set `annexsynconlyannex = true`.)
diff --git a/doc/todo/recent_change_to_fileRef_breaks_reinject_--known/comment_2_c1d232b0074296db4ce837169319dd41._comment b/doc/todo/recent_change_to_fileRef_breaks_reinject_--known/comment_2_c1d232b0074296db4ce837169319dd41._comment
new file mode 100644
index 0000000000..7a06b7279f
--- /dev/null
+++ b/doc/todo/recent_change_to_fileRef_breaks_reinject_--known/comment_2_c1d232b0074296db4ce837169319dd41._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="spwhitton"
+ avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
+ subject="comment 2"
+ date="2021-10-02T17:04:02Z"
+ content="""
+Thanks so much for the fix!  It looks like cherry-picking breaks the test suite, so I'll probably just wait for the next release.
+"""]]