public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/64968] Upgrade GCC Bugzilla to 5.0
Date: Mon, 27 Apr 2015 18:34:00 -0000	[thread overview]
Message-ID: <bug-64968-4-C8NK6wguY3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64968-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64968

--- Comment #14 from Frédéric Buclin <LpSolit at netscape dot net> ---
(In reply to Mikael Morin from comment #12)
> Hello, not sure this is due to the upgrade, but the attachment
> appears empty in the page:

That's unrelated to the upgrade. Your web browser is unable to display files of
type text/x-fortran, that's why.

What you want is https://bugzilla.mozilla.org/show_bug.cgi?id=622455


(In reply to Frank Ch. Eigler from comment #13)
> This appears to be due to CSS/JS goo marking that attachment textarea as
> "display: none !important" for some reason.

The reason being that you are looking at the "edit comment" field. So this
behavior is correct.
>From gcc-bugs-return-484775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Apr 27 18:52:26 2015
Return-Path: <gcc-bugs-return-484775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26518 invoked by alias); 27 Apr 2015 18:52:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25704 invoked by uid 48); 27 Apr 2015 18:52:23 -0000
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/64968] Upgrade GCC Bugzilla to 5.0
Date: Mon, 27 Apr 2015 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: mikael at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: LpSolit at netscape dot net
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64968-4-t0CvIH7uXS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg02327.txt.bz2
Content-length: 395

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64968

--- Comment #15 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to Frédéric Buclin from comment #14)
> That's unrelated to the upgrade. Your web browser is unable to display files
> of type text/x-fortran, that's why.
> 
> What you want is https://bugzilla.mozilla.org/show_bug.cgi?id=622455
> 
Ah OK.  Thanks.
>From gcc-bugs-return-484776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Apr 27 19:15:35 2015
Return-Path: <gcc-bugs-return-484776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71966 invoked by alias); 27 Apr 2015 19:15:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71906 invoked by uid 48); 27 Apr 2015 19:15:30 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65903] Line continuation followed by comment character in string fails to compile
Date: Mon, 27 Apr 2015 19:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to
Message-ID: <bug-65903-4-AmeKsvFZ5v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65903-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65903-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg02328.txt.bz2
Content-length: 517

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide903

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jvdelisle at gcc dot gnu.org

--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I will have a look.  Thanks for the report.


  parent reply	other threads:[~2015-04-27 18:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 14:23 [Bug web/64968] New: " LpSolit at netscape dot net
2015-02-07 14:44 ` [Bug web/64968] " trippels at gcc dot gnu.org
2015-02-09 10:39 ` LpSolit at netscape dot net
2015-02-09 11:43 ` fche at redhat dot com
2015-02-11 14:37 ` LpSolit at netscape dot net
2015-02-11 16:33 ` fche at redhat dot com
2015-02-11 20:46 ` LpSolit at netscape dot net
2015-02-11 20:48 ` LpSolit at netscape dot net
2015-04-18 18:30 ` LpSolit at netscape dot net
2015-04-27 15:13 ` mikael at gcc dot gnu.org
2015-04-27 17:39 ` fche at redhat dot com
2015-04-27 18:34 ` LpSolit at netscape dot net [this message]
2015-04-27 19:47 ` LpSolit at netscape dot net
2015-04-28 16:28 ` trippels at gcc dot gnu.org
2015-04-28 18:26 ` LpSolit at netscape dot net
2015-04-29 12:27 ` LpSolit at netscape dot net
2015-04-29 16:02 ` trippels at gcc dot gnu.org
2015-04-30 13:48 ` trippels at gcc dot gnu.org
2015-04-30 16:34 ` LpSolit at netscape dot net
2015-04-30 20:53 ` LpSolit at netscape dot net
2015-05-01  9:16 ` LpSolit at netscape dot net
2015-05-03  1:00 ` LpSolit at netscape dot net
2015-05-08  6:22 ` trippels at gcc dot gnu.org
2015-05-08  6:46 ` schwab@linux-m68k.org
2015-05-08  6:51 ` trippels at gcc dot gnu.org
2015-05-08 11:02 ` LpSolit at netscape dot net
2015-05-08 18:55 ` LpSolit at netscape dot net
2015-05-08 19:04 ` trippels at gcc dot gnu.org
2015-05-15 14:06 ` LpSolit at netscape dot net
2015-05-26 14:15 ` trippels at gcc dot gnu.org
2015-05-26 17:41 ` fche at redhat dot com
2015-07-13 10:49 ` trippels at gcc dot gnu.org
2015-09-25  9:05 ` trippels at gcc dot gnu.org
2015-09-26 15:28 ` LpSolit at netscape dot net

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-64968-4-C8NK6wguY3@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).