You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected there to be no mention of COMPAT_FREEBSDN ∈ N = [4-11], since this feature is useful only to binaries built on unsupported versions of FreeBSD running on a newer version (such as a static binary built on FreeBSD 4, or a dynamic binary with misc/compat4x in a jail).
What did you see instead?
A mention that Go is available for both FreeBSD 11, 12, and 13 since all three versions will be buildable by the port in the ports framework (and probably have already been built by the time this issue gets fixed).
Since this is an easy issue to fix, I hope it's okay that I didn't supply all the necessary information. :)
The text was updated successfully, but these errors were encountered:
ianlancetaylor
changed the title
[Documentation] Minor mistake regarding FreeBSD port applicability.
doc: release notes: minor mistake regarding FreeBSD port applicability
Sep 5, 2019
What version of Go are you using (
go version
)?1.13
Does this issue reproduce with the latest release?
Not applicable.
What operating system and processor architecture are you using (
go env
)?Not applicable.
What did you do?
Read the change log.
What did you expect to see?
I expected there to be no mention of COMPAT_FREEBSDN ∈ N = [4-11], since this feature is useful only to binaries built on unsupported versions of FreeBSD running on a newer version (such as a static binary built on FreeBSD 4, or a dynamic binary with misc/compat4x in a jail).
What did you see instead?
A mention that Go is available for both FreeBSD 11, 12, and 13 since all three versions will be buildable by the port in the ports framework (and probably have already been built by the time this issue gets fixed).
Since this is an easy issue to fix, I hope it's okay that I didn't supply all the necessary information. :)
The text was updated successfully, but these errors were encountered: