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: Fri, 08 Jun 2001 14:06:00 -0000	[thread overview]
Message-ID: <20010608210601.25026.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: Mark Mitchell <mark@codesourcery.com>
Cc: gerald@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: web/3044: Gnatsweb no longer working without Javascript
Date: Fri, 8 Jun 2001 15:39:08 -0400

 On Fri, Jun 08, 2001 at 02:16:01AM -0000, Mark Mitchell wrote:
 >  >>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:
 >  
 >      Phil> Phil P.S.- Anybody else think that high-priority PRs should
 >      Phil> be disallowed altogether during initial submission?  That a
 >  
 >  Yes -- but I don't know how to do that.
 
 For the record only:  complete guesswork, utterly untested (how could I test
 it?) patch against stock GNATS 1.113 sources follows.  One of these years
 there'll be enough time to persue this option with the gnats developers...
 
 String comparison tests written in decreasing order of likelihood, the
 idea is to fail as quickly as possible.
 
 
 --- pr.c.orig   Tue Mar  2 19:18:54 1999
 +++ pr.c        Wed Feb 28 16:37:48 2001
 @@ -747,6 +747,16 @@
           if (verify_enum (i, pr[i].value, token))
             found = TRUE;
 
 +         /* This hack prohibits random net submitters from submitting
 +             a high-priority PR; the idea is that maintainers should be
 +             the only ones permitted to raise priority to high.
 +             This should be more configurable. */
 +         if (found == TRUE && (!strcmp(pr[i].name,PRIORITY_STRING))
 +                            && (!strcmp(pr[i].value,"high"))
 +                            && (!strcmp(field_value(SUBMITTER),
 +                                        pr[SUBMITTER].default_value)))
 +           found = FALSE;
 +
           if (found == FALSE)
             {
               if (check)
 


             reply	other threads:[~2001-06-08 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 14:06 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-07 19:16 Mark Mitchell
2001-06-07 13:26 Phil Edwards
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=20010608210601.25026.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: 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).