public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	osv@javad.ru
Subject: Re: other/5718: Inconsistent and backwards incompatible handling of '-o' switch.
Date: Mon, 18 Feb 2002 23:49:00 -0000	[thread overview]
Message-ID: <20020219074945.11638.qmail@sources.redhat.com> (raw)

Synopsis: Inconsistent and backwards incompatible handling of '-o' switch.

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Mon Feb 18 23:49:42 2002
State-Changed-Why:
    Fixed for 3.1.  I'll try and get it in the patch set for 3.0.5, if such a beast ever gets released.

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


             reply	other threads:[~2002-02-19  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 23:49 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19 11:32 Zack Weinberg
2002-02-19 11:06 Neil Booth
2002-02-19 10:56 Zack Weinberg
2002-02-18 14:46 Nathan Sidwell
2002-02-18 14:26 Neil Booth
2002-02-18  4:26 osv

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=20020219074945.11638.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=osv@javad.ru \
    /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).