diff --git a/doc/bugs/Beware__58___there_is_a_file-losing_bug_in_unused_cmd.mdwn b/doc/bugs/Beware__58___there_is_a_file-losing_bug_in_unused_cmd.mdwn
new file mode 100644
index 0000000000..dbfe47ec6f
--- /dev/null
+++ b/doc/bugs/Beware__58___there_is_a_file-losing_bug_in_unused_cmd.mdwn
@@ -0,0 +1,15 @@
+### Please describe the problem.
+I ran git-annex unused on a few annexes and they dropped files that were still being used. The annexes were fully synced and git-annex list showed the files in the annex they were dropped from.
+
+### What steps will reproduce the problem?
+I'm not sure. The files lost appear to be more recently added files, so this bug must be in more recent versions. I will edit and fill this out when I know more.
+
+### What version of git-annex are you using? On what operating system?
+7.20191230-gef6d1e327 on Pop! OS 20.04 (Ubuntu based)
+
+### Please provide any additional information below.
+
+
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+I've used git-annex to maintain large file sets for years now and there is no better tool I know of.
diff --git a/doc/bugs/Patch_for_compilation_errors_on_Windows/comment_1_eb8d464da14af1fead372b4b61b20f17._comment b/doc/bugs/Patch_for_compilation_errors_on_Windows/comment_1_eb8d464da14af1fead372b4b61b20f17._comment
new file mode 100644
index 0000000000..d340c41376
--- /dev/null
+++ b/doc/bugs/Patch_for_compilation_errors_on_Windows/comment_1_eb8d464da14af1fead372b4b61b20f17._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="jwodder"
+ avatar="http://cdn.libravatar.org/avatar/b06e01332c949b895c681cc92934f36a"
+ subject="comment 1"
+ date="2020-11-23T15:02:28Z"
+ content="""
+I see you patched `Git/Hook.hs`, but you did not patch `Annex/Content/Presence.hs`.  The Windows builds are still failing.
+"""]]
diff --git a/doc/todo/does_not_preserve_timestamps/comment_12_a8b69299c9278c16c6c5061d88bc7eca._comment b/doc/todo/does_not_preserve_timestamps/comment_12_a8b69299c9278c16c6c5061d88bc7eca._comment
new file mode 100644
index 0000000000..afe36e709a
--- /dev/null
+++ b/doc/todo/does_not_preserve_timestamps/comment_12_a8b69299c9278c16c6c5061d88bc7eca._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Cebtenzzre"
+ avatar="http://cdn.libravatar.org/avatar/238202b8214db86e24636e11f4452a12"
+ subject="comment 12"
+ date="2020-11-22T16:07:15Z"
+ content="""
+The semantics described in [proposal for timestamp semantics](https://git-annex.branchable.com/bugs/proposal_for_timestamp_semantics/) would be all I need to stop wishing I just used rsync instead of git-annex. It seems easier to track history with rsync (snapshots and a CHANGELOG?) than to synchronize timestamps (or xattrs for comments) with git-annex. I don't care if it impacts performance, or if I have to set flags to non-default values, or how it resolves conflicts. I know git doesn't do it natively, but I thought the point of git-annex was to be better than native git with data files. Metadata like this is very useful to me, and often I want to sort by *some* kind of meaningful timestamp. ls can't read Exif or ID3 tags, and sometimes they aren't available or even relevant.
+"""]]