aboutsummaryrefslogtreecommitdiff
path: root/doc/tips/what_to_do_when_a_repository_is_corrupted
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-05-24 18:29:03 +0000
committerGravatar admin <admin@branchable.com>2014-05-24 18:29:03 +0000
commit9c014fce1dd716041e336e8b2a28259969a1b6be (patch)
treea89458fe5a620bc09c4cc4d6800a05098119911c /doc/tips/what_to_do_when_a_repository_is_corrupted
parent10141a176500a06f2cf482a9cbf7d9fb3e29dbb1 (diff)
Added a comment
Diffstat (limited to 'doc/tips/what_to_do_when_a_repository_is_corrupted')
-rw-r--r--doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment
new file mode 100644
index 000000000..870d7b93f
--- /dev/null
+++ b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.36"
+ subject="comment 3"
+ date="2014-05-24T18:29:03Z"
+ content="""
+@Maarten git clone from one of the other clones of the repository to the new drive. Also, recent versions of git-annex have a `git annex reinit` command that can be used to easily initialize a repository with the same settings as a repository that was lost.
+"""]]