public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: enrico.scholz@informatik.tu-chemnitz.de, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/3653: -fmessage-length=72 with g++ makes no sense
Date: Mon, 25 Nov 2002 07:16:00 -0000	[thread overview]
Message-ID: <20021119001436.27287.qmail@sources.redhat.com> (raw)

Synopsis: -fmessage-length=72 with g++ makes no sense

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Mon Nov 18 16:14:35 2002
State-Changed-Why:
    -fmessage-length has been in effect now for a long time and
    the default value of 72 will certainly not be changed to
    0. So let's close this, the discussion has been fought often
    enough.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3653


                 reply	other threads:[~2002-11-19  0:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021119001436.27287.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=enrico.scholz@informatik.tu-chemnitz.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).