From 164129b53d6ee77940da4adad09a28e698df1a3d Mon Sep 17 00:00:00 2001
From: jkniiv <jkniiv@web>
Date: Wed, 3 Aug 2022 15:47:08 +0000
Subject: [PATCH] Added a comment

---
 ..._4_07f1b2eacf7e9e58809ee44fc1d6b574._comment | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 doc/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_4_07f1b2eacf7e9e58809ee44fc1d6b574._comment

diff --git a/doc/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_4_07f1b2eacf7e9e58809ee44fc1d6b574._comment b/doc/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_4_07f1b2eacf7e9e58809ee44fc1d6b574._comment
new file mode 100644
index 0000000000..cfe2026977
--- /dev/null
+++ b/doc/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_4_07f1b2eacf7e9e58809ee44fc1d6b574._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="jkniiv"
+ avatar="http://cdn.libravatar.org/avatar/05fd8b33af7183342153e8013aa3713d"
+ subject="comment 4"
+ date="2022-08-03T15:47:07Z"
+ content="""
+@joey: No problem. Most of my git-annex use is rather vanilla (apart from annexing huge files) so I
+don't usually need the very latest in git-annex so I can always fall back to an earlier release/build.
+It's just that I like to keep track of git-annex's development and make sure it works on Windows most
+of the time which means I feel a need to build fresh versions and then kind of dogfood them as soon
+as possible. As a non-developer being able to report build errors and other bugs is my way of taking
+part in this project and hopefully in the process help make things smoother for the Windows user constituent
+that I represent.
+
+PS. Ikiwiki broke that link you made to my related todo. What's with that? The backlink appears in the todo,
+however.
+"""]]