From: Per Bothner <per@bothner.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: overseers@sources.redhat.com
Subject: Re: [gcc-announce-owner@gcc.gnu.org] Returned post for gcc-announce@gcc.gnu.org
Date: Thu, 06 Feb 2003 21:44:00 -0000 [thread overview]
Message-ID: <3E42D41E.2000502@bothner.com> (raw)
In-Reply-To: <87ptq5kswl.fsf@egil.codesourcery.com>
Zack Weinberg wrote:
> How do I get this posted to gcc-announce?
> Accordingly: #import and #pragma once will be removed from FSF GCC in
> 3.4. I will shortly send a patch to gcc-patches to implement that.
Please don't - I object to this change.
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/
prev parent reply other threads:[~2003-02-06 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 21:20 Zack Weinberg
2003-02-06 21:26 ` Jason Molenda
2003-02-06 21:32 ` Gerald Pfeifer
2003-02-06 21:36 ` Jason Molenda
2003-02-06 21:40 ` Christopher Faylor
2003-02-06 21:54 ` Zack Weinberg
2003-02-06 21:44 ` Per Bothner [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=3E42D41E.2000502@bothner.com \
--to=per@bothner.com \
--cc=overseers@sources.redhat.com \
--cc=zack@codesourcery.com \
/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).