summaryrefslogtreecommitdiff
path: root/doc/tips/recovering_from_a_corrupt_git_repository
diff options
context:
space:
mode:
authorGravatar http://id.clacke.se/ <clacke@web>2013-11-12 17:10:08 +0000
committerGravatar admin <admin@branchable.com>2013-11-12 17:10:08 +0000
commit38e399730a8ff3949d8a20d21420e940314fe95c (patch)
treed446376c7ea99a6dd53a63c36a3c2ffa592e8869 /doc/tips/recovering_from_a_corrupt_git_repository
parent913735db5a6686a9c3001049784ba15e321ec011 (diff)
Added a comment
Diffstat (limited to 'doc/tips/recovering_from_a_corrupt_git_repository')
-rw-r--r--doc/tips/recovering_from_a_corrupt_git_repository/comment_4_86e99017f7585ac2f76753051214637e._comment8
1 files changed, 8 insertions, 0 deletions
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 000000000..8d454fc3e
--- /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.
+"""]]