public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/108473] bugzilla see also should support gitlab.com URLs
Date: Mon, 04 Dec 2023 07:05:44 +0000 [thread overview]
Message-ID: <bug-108473-4-Xy0Rf5JHHq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108473-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108473
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Mark Wielaard from comment #7)
> OK, applied all 12 above commits to both both gcc and sourceware bugzilla.
> There were some small whitespace issues, but most applied cleanly.
>
> Could you check that everything looks fine and the new trackers can be added
> through See Also now?
GitLab links added to See Also without issue in bug 112380
prev parent reply other threads:[~2023-12-04 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 23:58 [Bug web/108473] New: " pinskia at gcc dot gnu.org
2023-01-19 23:59 ` [Bug web/108473] " pinskia at gcc dot gnu.org
2023-11-12 22:49 ` pinskia at gcc dot gnu.org
2023-11-12 23:00 ` sjames at gcc dot gnu.org
2023-11-20 10:31 ` mark at gcc dot gnu.org
2023-11-20 10:32 ` sjames at gcc dot gnu.org
2023-11-20 11:00 ` sjames at gcc dot gnu.org
2023-12-03 23:20 ` mark at gcc dot gnu.org
2023-12-03 23:24 ` mark at gcc dot gnu.org
2023-12-03 23:31 ` pinskia at gcc dot gnu.org
2023-12-04 7:05 ` egallager at gcc dot gnu.org [this message]
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-108473-4-Xy0Rf5JHHq@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).