public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "berndtrog at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/12720] New: Some suggestions for 'enter_bug.cgi'
Date: Wed, 22 Oct 2003 09:28:00 -0000	[thread overview]
Message-ID: <20031022091827.12720.berndtrog@yahoo.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12720

           Summary: Some suggestions for 'enter_bug.cgi'
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: web
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: berndtrog at yahoo dot com
                CC: gcc-bugs at gcc dot gnu dot org

This page "Enter a Bug -  http://gcc.gnu.org/bugzilla/enter_bug.cgi" could be
improved, IMO. (I'm a one-bug-in-a-year reporter)

1.
The link to the generic bug-page
"http://gcc.gnu.org/bugzilla/bugwritinghelp.html" is nice but an additional link
to http://gcc.gnu.org/bugs.html#report would be better.

2.
Host,Target,Build triplet should be linked to an explanation with one or two
examples.


What do you think?


             reply	other threads:[~2003-10-22  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22  9:28 berndtrog at yahoo dot com [this message]
2003-10-23  0:36 ` [Bug web/12720] " pinskia at gcc dot gnu dot org
2003-10-23  0:45 ` pinskia at gcc dot gnu dot org
2004-01-23  3:24 ` pinskia at gcc dot gnu dot org
2004-01-23 15:33 ` dberlin at gcc dot gnu dot org
2004-04-23 20:32 ` pinskia at gcc dot gnu dot org
2005-01-07 23:45 ` dberlin at gcc dot gnu dot org

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=20031022091827.12720.berndtrog@yahoo.com \
    --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).