summaryrefslogtreecommitdiff
path: root/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment')
-rw-r--r--doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment8
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment b/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment
deleted file mode 100644
index 6112bc089..000000000
--- a/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2012-01-06T03:08:28Z"
- content="""
-BTW, you'll want to \"make clean\", since the S3stub hack symlinks a file into place and it will continue building with S3stub even if you fix the problem until you clean.
-"""]]