public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: web/3044: Gnatsweb no longer working without Javascript
Date: Sun, 03 Jun 2001 17:16:00 -0000 [thread overview]
Message-ID: <E156hyq-0007yN-00@jsm28.trin.cam.ac.uk> (raw)
>Number: 3044
>Category: web
>Synopsis: Gnatsweb no longer working without Javascript
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: gerald
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jun 03 17:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.0 20010603 (prerelease)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:
As noted on overseers: gnatsweb is no longer working without
Javascript, whereas a few days ago it worked fine without Javascript
and after a fashion with lynx. This is a highly inopportune time to
break GNATS.
>How-To-Repeat:
Try to use gnatsweb without Javascript. Find that the "query" and
"advanced query" buttons do nothing.
>Fix:
Revert gnatsweb.pl to a working version if this can't be fixed
quickly.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-03 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-03 17:16 Joseph Myers [this message]
2001-06-07 4:42 gerald
2001-06-07 13:26 Phil Edwards
2001-06-07 19:16 Mark Mitchell
2001-06-08 14:06 Phil Edwards
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=E156hyq-0007yN-00@jsm28.trin.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-gnats@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).