From 1de12a291891463c6d532a10c74cbda1872c8b9b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 3 Mar 2011 16:58:52 -0400 Subject: document describe command --- .../what_to_do_when_you_lose_a_repository.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn (limited to 'doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn') 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 new file mode 100644 index 000000000..c914c1bb3 --- /dev/null +++ b/doc/walkthrough/what_to_do_when_you_lose_a_repository.mdwn @@ -0,0 +1,18 @@ +So you lost a thumb drive containing a git-annex repository. Or a hard +drive died or some other misfortune has befallen your data. + +Unless you configured backups, git-annex can't get your data back. But it +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 + +To remind yourself later what happened, you can change its description, too: + +# 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, +this lets git-annex tell you why a file is no longer accessible. -- cgit v1.2.3