summaryrefslogtreecommitdiff
path: root/gemfeed/2021-10-22-defensive-devops.gmi
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2023-08-27 13:59:11 +0300
committerPaul Buetow <paul@buetow.org>2023-08-27 13:59:11 +0300
commit3c030027337d10b308f8248aa3f753e1ded69007 (patch)
tree9004f72377d33e53eabe6615556179c1ee6d067f /gemfeed/2021-10-22-defensive-devops.gmi
parent0f46c32021cb9fdf87db18bd22de16fe03162f74 (diff)
change *buetow.org to paul.cyou
Diffstat (limited to 'gemfeed/2021-10-22-defensive-devops.gmi')
-rw-r--r--gemfeed/2021-10-22-defensive-devops.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2021-10-22-defensive-devops.gmi b/gemfeed/2021-10-22-defensive-devops.gmi
index 2cb54479..89b0af6a 100644
--- a/gemfeed/2021-10-22-defensive-devops.gmi
+++ b/gemfeed/2021-10-22-defensive-devops.gmi
@@ -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 your comments to paul at buetow.org :-)
+E-Mail your comments to `foo@paul.cyou` :-)
=> ../ Back to the main site