public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/55237] Please implement gcc.gnu.org/r123456 URL shorts for fast SVN revision access
Date: Tue, 22 Jan 2013 21:28:00 -0000 [thread overview]
Message-ID: <bug-55237-4-2HmVmRG0ai@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55237-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55237
--- Comment #7 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-22 21:27:59 UTC ---
(In reply to comment #6)
> It would be simpler to simply type r1234 in Bugzilla instead of
> http://gcc.gnu.org/r1234 and have it linkified to point to
> http://gcc.gnu.org/viewcvs?view=revision&revision=1234. Is that what you
> wanted? If not, then I have nothing to do about this bug.
Yes, linkifying r123456 is what I have in mind. Actually, the same as PR12345
does for links to Bugzilla.
next prev parent reply other threads:[~2013-01-22 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 10:46 [Bug web/55237] New: " ubizjak at gmail dot com
2012-11-08 22:01 ` [Bug web/55237] " steven at gcc dot gnu.org
2012-11-11 8:32 ` gerald at pfeifer dot com
2013-01-21 12:52 ` ubizjak at gmail dot com
2013-01-21 22:34 ` LpSolit at netscape dot net
2013-01-21 23:03 ` redi at gcc dot gnu.org
2013-01-22 21:24 ` LpSolit at netscape dot net
2013-01-22 21:28 ` ubizjak at gmail dot com [this message]
2013-04-18 16:29 ` LpSolit at netscape dot net
2013-05-15 8:24 ` [Bug web/55237] Linkify r123456 in comments to point to SVN steven at gcc dot gnu.org
2013-05-15 10:40 ` LpSolit at netscape dot net
2013-05-15 10:52 ` jakub at gcc dot gnu.org
2013-05-15 11:14 ` amonakov at gcc dot gnu.org
2013-05-15 11:17 ` LpSolit at netscape dot net
2013-05-15 11:46 ` stevenb.gcc at gmail dot com
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-55237-4-2HmVmRG0ai@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).