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 c++/56709] Should the passed command parameters result into the same error messages for a configuration test?
Date: Sun, 24 Mar 2013 14:59:00 -0000	[thread overview]
Message-ID: <bug-56709-4-Lne5NwnPvW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56709-4@http.gcc.gnu.org/bugzilla/>


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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-03-24 14:59:22 UTC ---
(In reply to comment #3)
> It seems that no other software developer was interested so far to add
> constructive feedback for this issue on the mailing list.

So ping the list again, bugzilla is not the right place to ask questions.

As I said, your question was unclear, you asked why there's a difference
between two commands and only show one command. Noone's going to waste their
time trying to answer you if your question is unclear and can't be understood.


      parent reply	other threads:[~2013-03-24 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 13:34 [Bug c++/56709] New: " Markus.Elfring at web dot de
2013-03-24 14:07 ` [Bug c++/56709] " redi at gcc dot gnu.org
2013-03-24 14:08 ` redi at gcc dot gnu.org
2013-03-24 14:48 ` Markus.Elfring at web dot de
2013-03-24 14:59 ` redi at gcc dot gnu.org [this message]

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-56709-4-Lne5NwnPvW@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).