-
Notifications
You must be signed in to change notification settings - Fork 18k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/build: rewrite Hg hashes in issue tracker #21088
Labels
Builders
x/build issues (builders, bots, dashboards)
help wanted
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Comments
/cc @kevinburke @andybons |
i generated a csv file mapping the comments/revisions to their corresponding git commits. (the mapping was generated with this failed to find a commit for a few of the revisions. i think it's because they came from a different repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Builders
x/build issues (builders, bots, dashboards)
help wanted
NeedsFix
The path to resolution is known, but the work has not been done.
Some old issues refer to mercurial hashes in their issue tracker. There is a mapping at https://golang.org/change/XXXXX and the git commits have this data too (as a golang-hg header in the commit), but if you don't know that it can be hard to track down.
Instead of people having to know this, one could rewrite all codesite URLs in the issue tracker to become googlesource.com URLs.
example: #2516 mentions http://code.google.com/p/go/source/detail?r=4e38cad33649.
The text was updated successfully, but these errors were encountered: