public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100140] Reference gcc development github mirror - Latest Development Build
Date: Mon, 19 Apr 2021 08:59:24 +0000 [thread overview]
Message-ID: <bug-100140-4-TgGkBymeKw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100140-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jignesh from comment #0)
> I am reproducing the comment posted there which gives entire details
> required for bug tracking and resolving. Unfortunately, no developers are
> responding to my messages on Github development builds since last 2 days
> hence posting here:
Because it's an unofficial mirror that has nothing to do with the GCC project.
No GCC developers are involved in it and nobody reads anything there.
next prev parent reply other threads:[~2021-04-19 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 4:52 [Bug c/100140] New: " j130496 at live dot co.uk
2021-04-19 8:34 ` [Bug c/100140] " jakub at gcc dot gnu.org
2021-04-19 8:59 ` redi at gcc dot gnu.org [this message]
2021-04-19 9:20 ` j130496 at live dot co.uk
2021-04-19 9:33 ` j130496 at live dot co.uk
2021-04-19 9:39 ` j130496 at live dot co.uk
2021-04-19 9:45 ` j130496 at live dot co.uk
2021-04-19 9:50 ` jakub at gcc dot gnu.org
2021-04-19 9:58 ` redi at gcc dot gnu.org
2021-04-19 10:06 ` j130496 at live dot co.uk
2021-04-19 10:10 ` redi at gcc dot gnu.org
2021-04-19 10:28 ` j130496 at live dot co.uk
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-100140-4-TgGkBymeKw@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).