public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sampo@symlabs.com
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7338: Error message contains newline, breaks grep -v; warning from include/g++-v3/bits/stl_threads.h
Date: Wed, 17 Jul 2002 11:46:00 -0000	[thread overview]
Message-ID: <20020717184602.2486.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7338; it has been noted by GNATS.

From: sampo@symlabs.com
To: Gabriel Dos Reis <gdr@codesourcery.com>
Cc: sampo@symlabs.com, gcc-gnats@gcc.gnu.org, miguel@symlabs.com
Subject: Re: c++/7338: Error message contains newline, breaks grep -v; warning from include/g++-v3/bits/stl_threads.h
Date: Wed, 17 Jul 2002 18:45:05 GMT

 Gabriel Dos Reis writes: 
 
 > sampo@symlabs.com writes: 
 > 
 > [...] 
 > 
 > | As can be seen "partly bracketed initializer" is on the next
 > | line, thus complicating ignoring it. World will be better
 > | place if error messages remain on single line. 
 > 
 > Use -fmessage-length=0.
 
 Thanks. That part understood. Now how about the warning from standard
 template library (include/g++-v3/bits/stl_threads.h)? 
 
 > -- Gaby
 
  --Sampo
 __________________________________________________________________
 SymLABS        DirectoryScript          www.symlabs.com
   e-nabling      triggers and stored      mobile=+351-918.731.007
   your biz       procedures for LDAP      fax=+351-214.222.637 
 


             reply	other threads:[~2002-07-17 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 11:46 sampo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-17 15:56 sampo
2002-07-17 12:46 Phil Edwards
2002-07-17  9:36 Gabriel Dos Reis
2002-07-17  8:46 sampo
2002-07-17  6:21 nathan
2002-07-17  5:56 sampo

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=20020717184602.2486.qmail@sources.redhat.com \
    --to=sampo@symlabs.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).