summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-03 17:24:46 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-03 17:24:46 -0400
commiteeadc2e3e041b77e409bfe258ebe6a778f70ccb5 (patch)
tree2c132ea761d3dd2e2651579a7146c6d5b14bfd6b
parentea4ea466f550b71ab389d6651c90bf521e30a1c1 (diff)
formatting
-rw-r--r--doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn b/doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn
index c914c1bb3..1159b2217 100644
--- a/doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn
+++ b/doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn
@@ -7,11 +7,11 @@ can help you deal with the loss.
First, go somewhere that knows about the lost repository, and mark it as
untrusted.
-# git annex untrust usbdrive
+ git annex untrust usbdrive
To remind yourself later what happened, you can change its description, too:
-# git annex describe usbdrive "USB drive lost in Timbuktu. Probably gone forever."
+ git annex describe usbdrive "USB drive lost in Timbuktu. Probably gone forever."
This retains the [[location_tracking]] information for the repository.
Maybe you'll find the drive later. Maybe that's impossible. Either way,