summaryrefslogtreecommitdiff
path: root/doc/tips/what_to_do_when_a_repository_is_corrupted
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmZilYULa6CDEGfuagoDlesyakBgnf-dF8 <Maarten@web>2014-05-23 23:50:58 +0000
committerGravatar admin <admin@branchable.com>2014-05-23 23:50:58 +0000
commit28c27ad3e066df75a7c633282b3f383d2a40ce3e (patch)
treee7be25fd4dd2c7d3d58a4e3c8356f9632bab832d /doc/tips/what_to_do_when_a_repository_is_corrupted
parent44e72fbefa3fc29008bfe710db5e0732b172dcdf (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_2_025178c2b11affe2d42a87544b897dc8._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment
new file mode 100644
index 000000000..beb177d00
--- /dev/null
+++ b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmZilYULa6CDEGfuagoDlesyakBgnf-dF8"
+ nickname="Maarten"
+ subject="comment 2"
+ date="2014-05-23T23:50:58Z"
+ content="""
+What if the drive is destroyed? How would I re-initialize a new drive to act as a substitute for the remote that was just lost?
+"""]]