From 14021185542dca5db29c5c51ab6925aea8632249 Mon Sep 17 00:00:00 2001
From: "http://id.clacke.se/" <clacke@web>
Date: Tue, 12 Nov 2013 17:10:08 +0000
Subject: [PATCH] Added a comment

---
 .../comment_4_86e99017f7585ac2f76753051214637e._comment   | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 doc/tips/recovering_from_a_corrupt_git_repository/comment_4_86e99017f7585ac2f76753051214637e._comment

diff --git a/doc/tips/recovering_from_a_corrupt_git_repository/comment_4_86e99017f7585ac2f76753051214637e._comment b/doc/tips/recovering_from_a_corrupt_git_repository/comment_4_86e99017f7585ac2f76753051214637e._comment
new file mode 100644
index 0000000000..8d454fc3e4
--- /dev/null
+++ b/doc/tips/recovering_from_a_corrupt_git_repository/comment_4_86e99017f7585ac2f76753051214637e._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://id.clacke.se/"
+ nickname="clacke"
+ subject="comment 4"
+ date="2013-11-12T17:10:06Z"
+ content="""
+Hm. This is bad. My hunch that btrfs was the culprit seems to have been wrong. After having switched things around, along with lots of `git annex sync` in various places, I now have a corrupt repo on ext4. It must be git or git-annex that does something wrong.
+"""]]