summaryrefslogtreecommitdiff
path: root/gemfeed/2021-10-22-defensive-devops.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2022-01-22 16:29:11 +0000
committerPaul Buetow <paul@buetow.org>2022-01-22 16:29:11 +0000
commitf6d87bb8ca599d0216a0d301807e659ace2a5250 (patch)
tree7f51f4d1319bd99781e93697a86b3c95abe6694c /gemfeed/2021-10-22-defensive-devops.md
parent6fe9c51b5b3bff4db4ebd6b315c4d89ef8c058cb (diff)
Publishing new version
Diffstat (limited to 'gemfeed/2021-10-22-defensive-devops.md')
-rw-r--r--gemfeed/2021-10-22-defensive-devops.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2021-10-22-defensive-devops.md b/gemfeed/2021-10-22-defensive-devops.md
index 260f88f2..e4e97028 100644
--- a/gemfeed/2021-10-22-defensive-devops.md
+++ b/gemfeed/2021-10-22-defensive-devops.md
@@ -99,6 +99,6 @@ For every major incident, you need to follow up with an incident retrospective.
This usually means creating one or more tickets, which will be dealt with soon. Once the permanent fix is deployed, you can remove your ad-hoc automation and monitoring around it and focus on your regular work again.
-E-Mail me your comments to snonux@snonux.de!
+E-Mail me your comments to paul at buetow dot org!
[Go back to the main site](../)