aboutsummaryrefslogtreecommitdiff
path: root/doc/devblog/day_288__microrelease_prep/comment_2_27a74d3926083a00c110aafea28420d7._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/devblog/day_288__microrelease_prep/comment_2_27a74d3926083a00c110aafea28420d7._comment')
-rw-r--r--doc/devblog/day_288__microrelease_prep/comment_2_27a74d3926083a00c110aafea28420d7._comment7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/devblog/day_288__microrelease_prep/comment_2_27a74d3926083a00c110aafea28420d7._comment b/doc/devblog/day_288__microrelease_prep/comment_2_27a74d3926083a00c110aafea28420d7._comment
new file mode 100644
index 000000000..461a86e8a
--- /dev/null
+++ b/doc/devblog/day_288__microrelease_prep/comment_2_27a74d3926083a00c110aafea28420d7._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="namelessjon"
+ subject="comment 2"
+ date="2015-05-28T10:14:45Z"
+ content="""
+https://stackoverflow.com/questions/1870696/simulate-a-faulty-block-device-with-read-errors ?
+"""]]