summaryrefslogtreecommitdiff
path: root/gemfeed/2021-10-22-defensive-devops.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2022-01-03 10:47:34 +0000
committerPaul Buetow <paul@buetow.org>2022-01-03 10:47:34 +0000
commitfcd39fad51d05c8f44b228d4ba8c0b0c34a7a6cf (patch)
treeb8e957117281a7f1d525c4b4258974d35400d4c5 /gemfeed/2021-10-22-defensive-devops.md
parent56dd12f6d891b5fd80426b91e34dab25dd389650 (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 de66c775..e97a2702 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 thoughts at snonux@snonux.de!
+E-Mail me your thoughts at sno@xo!
[Go back to the main site](../)