summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-10-22 18:12:45 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-10-22 18:12:45 -0400
commitf095430dfb9d0276e9cccca0d922b6621d7927cd (patch)
tree6f9665e071c04c98fe41737eed5c3336c4c39226
parent81de608447b0334ef84ebd74c380e4d0b3f6481b (diff)
update
-rw-r--r--doc/design/assistant/disaster_recovery.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/design/assistant/disaster_recovery.mdwn b/doc/design/assistant/disaster_recovery.mdwn
index ef6eb4730..f7e3482b2 100644
--- a/doc/design/assistant/disaster_recovery.mdwn
+++ b/doc/design/assistant/disaster_recovery.mdwn
@@ -69,6 +69,9 @@ files (see above), it should git fsck.
If git fsck finds problems, launch git repository repair.
+TODO: along with displaying alert when there is a problem, send an email
+alert. (Using system MTA?)
+
## git repository repair
There are several ways git repositories can get damanged.