From: Dmitri Shuralyov Date: Wed, 24 Jul 2024 17:30:28 +0000 (-0400) Subject: doc/next: use relative link to Go issue X-Git-Tag: go1.24rc1~1404 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=792a26130347c9b9db344ba56f86645679a1a9d9;p=gostls13.git doc/next: use relative link to Go issue The Go release notes are served on multiple domains (go.dev, golang.google.cn, tip.golang.org, localhost:8080 and so on), so links pointing to the Go website itself need to be relative to work in all those contexts. Caught by a test in x/website. The next CL adds the same test to this repository so these kinds of problems are caught sooner and with less friction. For #68545. Fixes #68575. Change-Id: I08056b98968c77a1d0ed93b63fccfbe41274ec8f Reviewed-on: https://go-review.googlesource.com/c/go/+/600656 Reviewed-by: Dmitri Shuralyov Auto-Submit: Dmitri Shuralyov Reviewed-by: Ian Lance Taylor LUCI-TryBot-Result: Go LUCI --- diff --git a/doc/next/3-tools.md b/doc/next/3-tools.md index 5ccade703f..b141287468 100644 --- a/doc/next/3-tools.md +++ b/doc/next/3-tools.md @@ -9,4 +9,4 @@ incompatible declarations. For instance, if `f` is declared as both `void f(int) and `void f(double)`, cgo will report an error instead of possibly generating an incorrect call sequence for `f(0)`. New in this release is a better detector for this error condition when the incompatible declarations appear in different -files. See [#67699](https://go.dev/issue/67699). +files. See [#67699](/issue/67699).