From 83eeb79a9a12eed3cf38acd3ac58010bbe2dc2db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Fri, 14 Oct 2022 08:20:59 +0200 Subject: [PATCH] fix broken links --- examples/block-net/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/block-net/README.md b/examples/block-net/README.md index e8e98a2..1aa6a69 100644 --- a/examples/block-net/README.md +++ b/examples/block-net/README.md @@ -1,6 +1,6 @@ # block-net -This [program](./main.go) explores the [question](https://twitter.com/rogpeppe/status/1359202847708037124) whether network i/o (e.g. waiting on socket read/write operations) will show up in the [block profiler](/block.md) or not. +This [program](./main.go) explores the [question](https://twitter.com/rogpeppe/status/1359202847708037124) whether network i/o (e.g. waiting on socket read/write operations) will show up in the [block profiler](../../block.md) or not. The program does the following: @@ -22,5 +22,5 @@ However, as you can see below, the block profiler [captures](./block.pb.gz) only ![block-net](./block-net.png) -This means that [block profiler](/block.md) is generally not able to give a good idea about goroutines that are waiting on network i/o. +This means that [block profiler](../../block.md) is generally not able to give a good idea about goroutines that are waiting on network i/o.