go1.12.16 not tagged on release-branch.go1.12?

122 views
Skip to first unread message

Steve Mynott

unread,
Jan 29, 2020, 6:30:23 AM1/29/20
to golan...@googlegroups.com
I don't see go1.12.16 tagged on release-branch.go1.12?

Is this expected?

--
Steve Mynott <steve....@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5

peterGo

unread,
Jan 29, 2020, 8:31:36 AM1/29/20
to golang-nuts
Steve,

"I don't see"

Please provide reproducible errors. For example,

[security] Go 1.13.7 and Go 1.12.16 are released
https://groups.google.com/forum/#!topic/golang-nuts/4uVpv5Zfxvo

~$ git clone https://github.com/golang/go --depth 1 -b release-branch.go1.12 go1.12
Cloning into 'go1.12'...
remote: Enumerating objects: 9305, done.
remote: Counting objects: 100% (9305/9305), done.
remote: Compressing objects: 100% (7682/7682), done.
remote: Total 9305 (delta 1465), reused 4643 (delta 1134), pack-reused 0
Receiving objects: 100% (9305/9305), 21.22 MiB | 11.94 MiB/s, done.
Resolving deltas: 100% (1465/1465), done.
~$ cd go1.12/src
~/go1.12/src$ ./make.bash
Building Go cmd/dist using /home/peter/go1.4.
Building Go toolchain1 using /home/peter/go1.4.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
Building packages and commands for linux/amd64.
---
Installed Go for linux/amd64 in /home/peter/go1.12
Installed commands in /home/peter/go1.12/bin
~/go1.12/src$ cd ../bin
~/go1.12/bin$ ./go version
go version go1.12.15 linux/amd64
~/go1.12/bin$

Peter

On Wednesday, January 29, 2020 at 6:30:23 AM UTC-5, Steve Mynott wrote:
I don't see go1.12.16 tagged on release-branch.go1.12?

Is this expected?

--
Steve Mynott <steve...@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5

Steve Mynott

unread,
Jan 29, 2020, 8:41:48 AM1/29/20
to peterGo, golang-nuts
Your example reproduces the error.

I'd expect ./go version to return

"go version go1.12.16 linux/amd64" since that's the latest version
>> Steve Mynott <steve...@gmail.com <javascript:>>
>> cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/3522d571-43da-48c3-8158-286ce7c4b092%40googlegroups.com.

peterGo

unread,
Jan 29, 2020, 8:55:48 AM1/29/20
to golang-nuts
Steve,

"Your example reproduces the error. "

Yes, I posted the error in reproducible form. The first step in fixing a bug. The Go team can confirm the bug and verify that their fix works. No guesswork required.

Peter
Steve Mynott <steve...@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5

Sue Spence

unread,
Jan 29, 2020, 9:25:49 AM1/29/20
to golang-nuts
I saw a person asking a question, not submitting a bug. There was a certain something about your response, that fronted as helpful but didn't really come across that way. 

Tyler Compton

unread,
Jan 29, 2020, 12:49:02 PM1/29/20
to peterGo, golang-nuts
I think it's very reasonable to ask a simple Git workflow question on golang-nuts without having to provide reproduction steps.

Yes, I posted the error in reproducible form. The first step in fixing a bug. The Go team can confirm the bug and verify that their fix works. No guesswork required.

I think you're unintentionally coming off as condescending.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.

Steve Mynott

unread,
Jan 31, 2020, 2:00:18 AM1/31/20
to Tyler Compton, peterGo, golang-nuts

peterGo

unread,
Jan 31, 2020, 1:59:33 PM1/31/20
to golang-nuts
Sue,

I saw a person reporting a bug, mistake, or inconsistency, which I confirmed. Filing a ticket on the Go issue tracker asks for a recipe for reproducing the error.

The Go Project
https://golang.org/project/

Reporting issues
https://github.com/golang/go/issues

If you spot bugs, mistakes, or inconsistencies in the Go project's code or documentation, please let us know by filing a ticket on our issue tracker.

filing a ticket: https://github.com/golang/go/issues/new

Peter
Reply all
Reply to author
Forward
0 new messages