public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/52228] Bugzilla: Missing link for "PR...."
Date: Mon, 13 Feb 2012 16:24:00 -0000	[thread overview]
Message-ID: <bug-52228-4-y9Kfm916yI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52228-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52228

--- Comment #9 from Frédéric Buclin <LpSolit at netscape dot net> 2012-02-13 16:24:20 UTC ---
(In reply to comment #8)
> Regarding comment 0, how about such a pattern:
> 
> qr/(?<!\D/)\b(pr(?:\s*|\s+\S+\/)(\d+)(?:\s+comment\s+(\d+))?)/i

This is just a hack. Not a good idea.


> Best would be a pattern, which only prohibits "http(s):"[nonwhitespace]/PR".

Of course, but negative look-behind assertions only accept fixed-width strings.
Else I would simply look for :// in the string. I have a workaround which I'm
discussing upstream.


  parent reply	other threads:[~2012-02-13 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:43 [Bug web/52228] New: " burnus at gcc dot gnu.org
2012-02-13 11:11 ` [Bug web/52228] " rguenth at gcc dot gnu.org
2012-02-13 15:29 ` LpSolit at netscape dot net
2012-02-13 15:32 ` LpSolit at netscape dot net
2012-02-13 15:40 ` redi at gcc dot gnu.org
2012-02-13 15:41 ` redi at gcc dot gnu.org
2012-02-13 15:44 ` redi at gcc dot gnu.org
2012-02-13 16:00 ` LpSolit at netscape dot net
2012-02-13 16:17 ` burnus at gcc dot gnu.org
2012-02-13 16:24 ` LpSolit at netscape dot net [this message]
2012-02-13 17:51 ` LpSolit at netscape dot net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52228-4-y9Kfm916yI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).