From: Dave Allured - NOAA Affiliate <dave.allured@noaa.gov>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Problems with GCC's Bugzilla?
Date: Wed, 25 Sep 2013 16:08:00 -0000 [thread overview]
Message-ID: <CALqwTFMyKbYf6tk6jH_UE_EkGr1c8XaYkUA4huxXzHPF1fFDUA@mail.gmail.com> (raw)
In-Reply-To: <19EB96622A777C4AB91610E763265F462BB245@SJEXCHMB14.corp.ad.broadcom.com>
On Wed, Sep 25, 2013 at 10:01 AM, Paulo Matos <pmatos@broadcom.com> wrote:
>> -----Original Message-----
>> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
>> Behalf Of Vincent Lefevre
>> Sent: 25 September 2013 16:51
>> To: gcc-help@gcc.gnu.org
>> Subject: Problems with GCC's Bugzilla?
>>
>> Hi,
>>
>> Am I the only one having problems with GCC's Bugzilla? Either empty
>> pages or empty CSS (with Firefox) or server error (with Chromium).
>> Actually I could reproduce these problems only on the following page:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21718
>>
>> Other pages don't seem to be affected.
>
>
> My firefox (Windows 24.0) doesn't like that page either. Weird!
>
> I have no explanation for it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21718
Displays correctly for me in Safari 6.0.5 on Mac OS 10.8.5 (x86_64).
If someone (not me) wants to analyze the page source code, I can
capture it and send it to you.
--Dave
next prev parent reply other threads:[~2013-09-25 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 15:51 Vincent Lefevre
2013-09-25 16:01 ` Paulo Matos
2013-09-25 16:07 ` Paulo Matos
2013-09-25 16:08 ` Dave Allured - NOAA Affiliate [this message]
2013-09-25 16:12 ` Dave Allured - NOAA Affiliate
2013-09-25 17:13 ` Vincent Lefevre
2013-09-25 16:07 ` Jonathan Wakely
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=CALqwTFMyKbYf6tk6jH_UE_EkGr1c8XaYkUA4huxXzHPF1fFDUA@mail.gmail.com \
--to=dave.allured@noaa.gov \
--cc=gcc-help@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).