From e847f2b659d6761a471b0acfdfa6301ab37fd5e5 Mon Sep 17 00:00:00 2001 From: mlimber Date: Fri, 10 May 2019 17:06:21 -0400 Subject: [PATCH] Make links pretty --- _posts/2019-05-10-totw-90.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_posts/2019-05-10-totw-90.md b/_posts/2019-05-10-totw-90.md index 541e65c4..352f36b7 100644 --- a/_posts/2019-05-10-totw-90.md +++ b/_posts/2019-05-10-totw-90.md @@ -14,7 +14,7 @@ Originally posted as TotW #90 on March 19, 2015 One of the frustrating things about our (mis)use of command-line flags is the difficulty in removing a flag from binary and production -servers safely (revisit https://abseil.io/tips/45 for some frustrating +servers safely (revisit [TotW #45](https://abseil.io/tips/45) for some frustrating misuses). The trouble? A binary won’t start if you specify a flag that is no longer defined, and thus removal of flags may require coordination between C++ code and your job launching scripts and configurations. @@ -38,7 +38,7 @@ for a very simple flag retirement could look like this: 1. Remove uses of `FLAGS_frobber` from code. - If you’re following the advice of https://abseil.io/tips/45 and using + If you’re following the advice of [TotW #45](https://abseil.io/tips/45) and using flags primarily from `main()` this should be easy to do and to check for. @@ -71,4 +71,4 @@ most complicated flag removals can be enabled safely with this system. So, the next time you’re wondering how to remove a flag safely, consider retiring it first and taking it step-by-step. -[1]: https://github.com/abseil/abseil-cpp/blob/master/absl/flags/flag.h#L255 \ No newline at end of file +[1]: https://github.com/abseil/abseil-cpp/blob/master/absl/flags/flag.h#L255