public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/54973] [bugzilla] make "Before reporting a bug" notice more prominent
Date: Thu, 18 Oct 2012 13:00:00 -0000	[thread overview]
Message-ID: <bug-54973-4-SyXaar8OJP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54973-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-10-18 13:00:34 UTC ---
I was assuming it would be visible to everyone because it's harmless and can be
ignored (I'm sure many users will still ignore it!) but if other privileged
users don't want to see it and it's easy to do then it could be hidden from
them


  parent reply	other threads:[~2012-10-18 13:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 12:42 [Bug web/54973] New: " redi at gcc dot gnu.org
2012-10-18 12:51 ` [Bug web/54973] " LpSolit at netscape dot net
2012-10-18 13:00 ` redi at gcc dot gnu.org [this message]
2012-10-18 13:27 ` redi at gcc dot gnu.org
2012-10-18 13:38 ` LpSolit at netscape dot net
2012-10-18 13:49 ` redi at gcc dot gnu.org
2012-10-23 10:29 ` redi at gcc dot gnu.org
2012-10-26 15:21 ` redi at gcc dot gnu.org
2012-10-26 15:25 ` pinskia at gcc dot gnu.org
2012-10-26 15:28 ` LpSolit at netscape dot net
2012-10-26 15:47 ` ian at airs dot com
2012-10-26 16:04 ` LpSolit at netscape dot net
2012-10-26 16:07 ` LpSolit at netscape dot net
2012-10-26 16:48 ` pinskia at gcc dot gnu.org
2012-10-26 16:53 ` redi at gcc dot gnu.org
2012-10-26 16:58 ` LpSolit at netscape dot net
2012-10-27  0:55 ` ian at airs dot com
2012-10-27  0:57 ` pinskia at gcc dot gnu.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=bug-54973-4-SyXaar8OJP@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).