public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com> To: gerald@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: web/3044: Gnatsweb no longer working without Javascript Date: Thu, 07 Jun 2001 13:26:00 -0000 [thread overview] Message-ID: <20010607202600.22951.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR web/3044; it has been noted by GNATS. From: Phil Edwards <pedwards@disaster.jaj.com> To: gerald@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk Subject: Re: web/3044: Gnatsweb no longer working without Javascript Date: Thu, 7 Jun 2001 15:05:47 -0400 On Thu, Jun 07, 2001 at 11:42:57AM -0000, gerald@gcc.gnu.org wrote: > State-Changed-Why: > Fixed, properly (instead of the original workaround), by > upgrading to gnatsweb 2.8.1. I'll just pause to note that after submitting a change to a PR, I see "warning: refresh URL is not absolute" from the browser I use for gnats. Everything still works, though. Phil P.S.- Anybody else think that high-priority PRs should be disallowed altogether during initial submission? That a PR should have to be /changed/ to be high? Just a pet peeve of mine... -- pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com devphil at several other less interesting addresses in various dot domains The gods do not protect fools. Fools are protected by more capable fools.
next reply other threads:[~2001-06-07 13:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-07 13:26 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-08 14:06 Phil Edwards 2001-06-07 19:16 Mark Mitchell 2001-06-07 4:42 gerald 2001-06-03 17:16 Joseph Myers
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=20010607202600.22951.qmail@sourceware.cygnus.com \ --to=pedwards@disaster.jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=gerald@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: linkBe 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).