summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/design/assistant/disaster_recovery.mdwn3
-rw-r--r--doc/devblog/day_41__onward.mdwn2
2 files changed, 5 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.
diff --git a/doc/devblog/day_41__onward.mdwn b/doc/devblog/day_41__onward.mdwn
index 4ee27c92c..fd393b734 100644
--- a/doc/devblog/day_41__onward.mdwn
+++ b/doc/devblog/day_41__onward.mdwn
@@ -13,3 +13,5 @@ problems.
[[!img /assistant/brokenrepositoryalert.png]]
[[!img /assistant/repairrepository.png]]
+
+[[!meta title="the user interface I hope noone ever sees"]]