From 83df094c3650246f2efd2eb2d56f70916fa05ade Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@joeyh.name>
Date: Tue, 12 Jul 2016 14:32:40 -0400
Subject: [PATCH] comment

---
 ...nt_3_8a563d9ccba5e912713812c77d34ea1f._comment | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 doc/bugs/does_not_build_on_OpenBSD_5.9/comment_3_8a563d9ccba5e912713812c77d34ea1f._comment

diff --git a/doc/bugs/does_not_build_on_OpenBSD_5.9/comment_3_8a563d9ccba5e912713812c77d34ea1f._comment b/doc/bugs/does_not_build_on_OpenBSD_5.9/comment_3_8a563d9ccba5e912713812c77d34ea1f._comment
new file mode 100644
index 0000000000..87b1c4c127
--- /dev/null
+++ b/doc/bugs/does_not_build_on_OpenBSD_5.9/comment_3_8a563d9ccba5e912713812c77d34ea1f._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-07-12T18:31:17Z"
+ content="""
+Not sure if that stack bug you linked to is quite a match for what it's
+doing, so I opened a new one:
+<https://github.com/commercialhaskell/stack/issues/2371>
+
+I don't currently see anything I could do in git-annex to avoid this
+problem.
+
+What version of stack are you using? It could be that a newer version of
+stack doesn't have the problem.
+"""]]