summaryrefslogtreecommitdiff
path: root/doc/design/assistant
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-10-18 15:27:20 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-10-18 15:27:20 -0400
commit711786ee02b520795348be0f8745264eebc50ddc (patch)
tree3171bc156c949db8fd6dc7e575e50f0c9dcef7b4 /doc/design/assistant
parentdcdbfc62fc4f9a7ba9e1391743cfac2e333c1c49 (diff)
update
Diffstat (limited to 'doc/design/assistant')
-rw-r--r--doc/design/assistant/disaster_recovery.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/design/assistant/disaster_recovery.mdwn b/doc/design/assistant/disaster_recovery.mdwn
index 1bc594e64..67054273e 100644
--- a/doc/design/assistant/disaster_recovery.mdwn
+++ b/doc/design/assistant/disaster_recovery.mdwn
@@ -1,6 +1,8 @@
The assistant should help the user recover their repository when things go
wrong.
+[[!toc ]]
+
## dangling lock files
There are a few ways a git repository can get broken that are easily fixed.
@@ -80,6 +82,9 @@ clone the remote, sync from all other remotes, move over .git/config and
it. This should be automatable and get the user back on their feet. User
could just click a button and have this be done.
+This is useful outside git-annex as well, so make it a
+git-recover-repository command.
+
### detailed design
Run `git fsck` and parse output to find bad objects, and determine