https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93185
Frédéric Buclin <LpSolit at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |LpSolit at gmail dot com
--- Comment #8 from Frédéric Buclin <LpSolit at gmail dot com> ---
(In reply to Jakub Jelinek from comment #7)
> r([0-9]{1,6}) to http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=\1
> (what we have already, should be https? and perhaps we'll switch to some
> redirector instead, so maybe https://gcc.gnu.org/r\1 instead?)
I have updated Bugzilla to point to https instead of http. Which URL do you
prefer: the current link to viewcvs/gcc?view=revision&revision=\1 or the link
to the redirector https://gcc.gnu.org/r\1 ? The advantage of the link to
viewcvs is that you have one less redirection.
> pr([0-9]{1,6}) etc. to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=\1 (also
> implemented, similar PR [a-z-]+/([0-9]{1,6}) )
What's the point of [a-z]+/ in front of the bug ID if this part is useless to
identify the bug report? I haven't implemented that part till I understand what
this part is used for.
> (r[0-9]{1,2}-[0-9]{1,6}) to https://gcc.gnu.org/\1 (redirector to be
> implemented)
Waiting for the redirector to be implemented. Could meanwhile someone paste a
valid example here so that I can use it for testing?
> g:([0-9a-zA-Z_-]+) to https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=\1
Done, but I have restricted the regexp to ([0-9a-f]{7,40}) as the hash is in
hexadecimal form, so we don't need (nor want) g-z A-Z _ and -.
For testing purposes: g:d3cf980217ce13b1eda01d4c42a7e3afd2bf3217 g:d3cf9802
g:01invalid234hash567
> r[0-9]{1,2}-[0-9]{1,6}-g([0-9a-f]{7,40}) to
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=\1
> ?
Could someone paste a valid example here so that I can test it too?
