summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-01-13 20:27:35 +0000
committerGravatar admin <admin@branchable.com>2014-01-13 20:27:35 +0000
commit11de155f62afdb13e1ac97cd2da4f0b0fb0edcaa (patch)
tree1078da15e4304c7a965373f58c51365ef208fe69
parent25d87e8df5733f162be215825a05955c8513eb8c (diff)
Added a comment
-rw-r--r--doc/forum/Git_annex___39__corrupting__39___itself/comment_4_45974f60a81ed2d00b87ffb1a7963c6f._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/Git_annex___39__corrupting__39___itself/comment_4_45974f60a81ed2d00b87ffb1a7963c6f._comment b/doc/forum/Git_annex___39__corrupting__39___itself/comment_4_45974f60a81ed2d00b87ffb1a7963c6f._comment
new file mode 100644
index 000000000..4328f5d24
--- /dev/null
+++ b/doc/forum/Git_annex___39__corrupting__39___itself/comment_4_45974f60a81ed2d00b87ffb1a7963c6f._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.43"
+ subject="comment 4"
+ date="2014-01-13T20:27:34Z"
+ content="""
+Many problems of this sort can happen if the disk that the git reposotory is on is losing data that's written to it, or is just removed (or the computer crashes) at the wrong time. `git-annex repair` can be run in the repository to recover from many problems like this, and it's getting better all the time.
+"""]]