The linked mirror file does not exist (yet?)

Hm, nice catch. Should I remove it? We can also switch to use GitHub releases as the mirror.

I don't know, but to me it sounds better to switch to GitHub releases
instead of removing the mirror link.

On Wednesday, 19 October 2016, Francisco Souza notifications@github.com
wrote:

Hm, nice catch. Should I remove it? We can also switch to use GitHub
releases as the mirror.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6096 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAifhPypU5DBHSv6ePENvJ2lWH3F9MQwks5q1oepgaJpZM4KbZlW
.

Peter Hellberg
Go and Ruby Developer, Code7 Interactive

In general, mirror links that do not exist yet are fine as long as the server itself is still alive.

Cool, looks like the website is live and it will eventually sync.

In case anyone wonders, https://go.googlesource.com/tools/+log/release-branch.go1.7 hasn't been updated, so no need to update the gotools resource.

Merged as c615b9c. Thank you for your contribution to Homebrew!

@zmwangx I think that the primary location of Go source is on github: https://github.com/golang/go/tree/release-branch.go1.7.

I'm not sure how they manage it tho.

I'm talking about the gotools resource, not golang/go.

Oh, I see. Sorry about that x)