public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikestump at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/53028] add dg-pedantic
Date: Wed, 18 Apr 2012 22:47:00 -0000	[thread overview]
Message-ID: <bug-53028-4-MwhoevNgtY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53028-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Mike Stump <mikestump at comcast dot net> 2012-04-18 22:42:55 UTC ---
So, do you have a pointer to where a maintainer said that they require 3
duplicates for a piece of work?  For all similar future work?  They usually
say, please include a testcase, meaning, one testcase.  One is certainly
reasonable.  For some work, for some cases, they might want 2 or 3 testcases,
but, those I suspect should be rare to very rare.  The requirements for 3 for
that change should not be read as to be generally require 3 for all future
changes...  or, at least, that'd be my interpretation.


  parent reply	other threads:[~2012-04-18 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  9:19 [Bug testsuite/53028] New: " manu at gcc dot gnu.org
2012-04-18  9:23 ` [Bug testsuite/53028] " manu at gcc dot gnu.org
2012-04-18 17:37 ` mikestump at comcast dot net
2012-04-18 18:28 ` manu at gcc dot gnu.org
2012-04-18 20:04 ` mikestump at comcast dot net
2012-04-18 21:48 ` manu at gcc dot gnu.org
2012-04-18 22:47 ` mikestump at comcast dot net [this message]
2012-04-19  7:06 ` manu at gcc dot gnu.org
2012-04-23 21:38 ` joseph at codesourcery dot com
2012-04-24  0:31 ` mikestump at comcast dot net
2012-04-28  0:03 ` manu at gcc dot gnu.org
2012-04-30  1:08 ` mikestump at comcast dot net

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-53028-4-MwhoevNgtY@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).