public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: davidc@freebsd.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	ljrittle@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libobjc/8562: minor bugs in runtime installed header files
Date: Wed, 26 Mar 2003 08:06:00 -0000	[thread overview]
Message-ID: <20030326075943.27201.qmail@sources.redhat.com> (raw)

Synopsis: minor bugs in runtime installed header files

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Wed Mar 26 07:59:42 2003
Responsible-Changed-Why:
    Mine (only because it had FreeBSD in it).
State-Changed-From-To: open->closed
State-Changed-By: ljrittle
State-Changed-When: Wed Mar 26 07:59:42 2003
State-Changed-Why:
    This patch looks fine to me David.  I will post it to gcc-patches@gcc.gnu.org (CC'ing you) in the proper form for review by the [lib]objc maintainers.  Here is a test case (we normally like them in addition to patches and I will include it):
    #include <objc/hash.h>
    #include <objc/objc-list.h>
    Add this flag to see the problem when installed from FSF tree: -Wsystem-headers
    FYI, I'm closing this PR before commit since strictly speaking this
    problem only appears to affect non-FSF installs.  I will include
    some commentary with the patch.

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


             reply	other threads:[~2003-03-26  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26  8:06 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 18:41 davidc

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=20030326075943.27201.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=davidc@freebsd.org \
    --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).