diff --git a/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_6_0b316eb8b0436350ce7fbec5093975d1._comment b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_6_0b316eb8b0436350ce7fbec5093975d1._comment
new file mode 100644
index 0000000000..ea6b1c9082
--- /dev/null
+++ b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_6_0b316eb8b0436350ce7fbec5093975d1._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="git-annex build-time dependencies"
+ date="2020-02-18T19:33:32Z"
+ content="""
+\"git-annex makes similar assumptions about eg, `cp --reflink` being supported or not, and I don't think it's very unusual to probe OS features at compile time\" -- this works well for package managers tied to specific distros.  But consider something like [[install/conda]] that creates packages meant to be installed on a variety of systems.  I can add a run-time dependency on `coreutils` to ensure that `cp --reflink` works, but I'm a bit wary about requiring git-annex users to replace all core utils with conda-forge ones.  For one, these may be slower, being compiled for a generic architecture. For two, if they're not fully backwards-compatible, they make break some assumptions relied on by other parts of the distro.
+"""]]
diff --git a/doc/special_remotes/comment_42_85e354eb058aea02be7b847bceb02313._comment b/doc/special_remotes/comment_42_85e354eb058aea02be7b847bceb02313._comment
new file mode 100644
index 0000000000..a4a30ba026
--- /dev/null
+++ b/doc/special_remotes/comment_42_85e354eb058aea02be7b847bceb02313._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="Dan"
+ avatar="http://cdn.libravatar.org/avatar/986de9e060699ae70ff7c31342393adc"
+ subject="Avoid fetching from special remotes"
+ date="2020-02-19T00:22:04Z"
+ content="""
+I have a few special remotes configured in my git annex-ed repo. As far as `git` is concerned, these are just ordinary remotes (they have entries in the `.git/config` file). As a result, when I do something like `git fetch --all` it still tries to fetch from them. This of course fails (since they aren't actually git repositories). It isn't the end of the world, but causes some extra noise in my output (I use `magit` in emacs for most of my `git` workflow, so I have to drill down a bit to see what actually failed and then dismiss it as an expected failure).
+
+It'd be nice if I could just prevent `git` from fetching from these special remotes. Is there a clever way I can set `remote.<name>.fetch` in the local config so as to leave these remotes alone when fetching?
+"""]]
diff --git a/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_10_06fd59c8bdd451b5608e1e0191f4d5cb._comment b/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_10_06fd59c8bdd451b5608e1e0191f4d5cb._comment
new file mode 100644
index 0000000000..d40c0915d2
--- /dev/null
+++ b/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_10_06fd59c8bdd451b5608e1e0191f4d5cb._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="thanks"
+ date="2020-02-18T20:00:11Z"
+ content="""
+\"--no-content combined with --only-annex. Now implemented\" -- thanks a lot, I was also looking for that.
+"""]]