-
Leigh McCulloch authored
The go repository contains a mix of github.com/golang/go/issues/xxxxx and golang.org/issues/xxxxx URLs for references to issues in the issue tracker. We should use one for consistency, and golang.org is preferred in case the project moves the issue tracker in the future. This reasoning is taken from a comment Sam Whited left on a CL I recently opened: https://go-review.googlesource.com/c/go/+/73890. In that CL I referenced an issue using its github.com URL, because other tests in the file I was changing contained references to issues using their github.com URL. Sam Whited left a comment on the CL stating I should change it to the golang.org URL. If new code is intended to reference issues via golang.org and not github.com, existing code should be updated so that precedence exists for contributors who are looking at the existing code as a guide for the code they should write. Change-Id: I3b9053fe38a1c56fc101a8b7fd7b8f310ba29724 Reviewed-on: https://go-review.googlesource.com/75673Reviewed-by:
Brad Fitzpatrick <bradfitz@golang.org>
8db19a49
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
elliptic.go | ||
elliptic_test.go | ||
p224.go | ||
p224_test.go | ||
p256.go | ||
p256_amd64.go | ||
p256_asm_amd64.s | ||
p256_asm_s390x.s | ||
p256_generic.go | ||
p256_s390x.go |