summaryrefslogtreecommitdiff
path: root/doc/use_case/Bob.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-04 12:45:09 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-04 12:45:09 -0400
commit2a56d012f7e2db7b8fb8b5e70425c34187f4589d (patch)
tree6a024262e0e1441e529a66171c0bf2363e683cc0 /doc/use_case/Bob.mdwn
parent69c14d130bc7a754e3a4fa184ff317690ad48ca6 (diff)
format
Diffstat (limited to 'doc/use_case/Bob.mdwn')
-rw-r--r--doc/use_case/Bob.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/use_case/Bob.mdwn b/doc/use_case/Bob.mdwn
index 53c09bc18..5982b5fcb 100644
--- a/doc/use_case/Bob.mdwn
+++ b/doc/use_case/Bob.mdwn
@@ -11,15 +11,15 @@ without worry about accidentally deleting anything.
When Bob needs access to some files, git-annex can tell him which drive(s)
they're on, and easily make them available. Indeed, every drive knows what
is on every other drive.
-([[more about location tracking|location_tracking]])
+[[more about location tracking|location_tracking]]
Bob thinks long-term, and so he's glad that git-annex uses a simple
repository format. He knows his files will be accessible in the future
even if the world has forgotten about git-annex and git.
-([[more about future-proofing|future_proofing]])
+[[more about future-proofing|future_proofing]]
Run in a cron job, git-annex adds new files to archival drives at night. It
also helps Bob keep track of intentional, and unintentional copies of
files, and logs information he can use to decide when it's time to duplicate
the content of old drives.
-([[more about backup copies|copies]])
+[[more about backup copies|copies]]