From: Martin Sebor <msebor@gmail.com>
To: Overseers mailing list <overseers@sourceware.org>,
"overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Cc: Thomas Koenig <tkoenig@netcologne.de>
Subject: Re: Strange gcc bugzilla errors
Date: Tue, 30 Jun 2020 08:52:06 -0600 [thread overview]
Message-ID: <bd1e0261-c024-bc98-95cb-b1c93ef31e7c@gmail.com> (raw)
In-Reply-To: <4914173f-ab83-fa8f-ed3c-9c1eb3cde4d5@netcologne.de>
On 6/30/20 1:47 AM, Thomas Koenig via Overseers wrote:
> Hi,
>
> since today, I keep getting strange bugzilla errors when submitting
> a comment to the gcc bugzilla. The comments do appear.
>
> One example where this happened is
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95366#c4
>
> Here is the error message:
>
> Software error:
>
> Invalid Content-Type 'subtype' parameter at Bugzilla/BugMail.pm line 471.
>
> For help, please send mail to the webmaster (root@localhost), giving
> this error message and the time and date of the error.
Just confirming that I have seen the same error yesterday.
Comment #5 is a duplicate of c#4. I submitted it twice
thinking the error was transient. I got it after both
submissions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95940
Martin
prev parent reply other threads:[~2020-06-30 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 7:47 Thomas Koenig
2020-06-30 14:52 ` Martin Sebor [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=bd1e0261-c024-bc98-95cb-b1c93ef31e7c@gmail.com \
--to=msebor@gmail.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.org \
--cc=tkoenig@netcologne.de \
/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).