public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/3336 Date: Mon, 09 Jul 2001 14:16:00 -0000 [thread overview] Message-ID: <20010709211604.22326.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/3336; it has been noted by GNATS. From: Nathan Sidwell <nathan@codesourcery.com> To: Travis Smith <TSmith@hy-tekmail.net> Cc: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, "'tazium@yahoo.com'" <tazium@yahoo.com> Subject: Re: c++/3336 Date: Mon, 09 Jul 2001 22:14:16 +0100 Travis Smith wrote: > > Here's the preprocessor for it. You've provided the cpp output, but your mail has the following boilerplate on it. > This email is confidential and intended solely for the use of the individual > to whom it is addressed. Any views or opinions presented are solely those > of the author and do not necessarily represent those of Hy-Tek Material > Handling . > If you are not the intended recipient, be advised that you have received > this email in error and that any use, dissemination, forwarding, printing, > or copying of this email is strictly prohibited. > > If you have received this email in error please contact the sender. can you confirm that 'comm.ii' is not confidential? nathan -- Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC 'But that's a lie.' - 'Yes it is. What's your point?' nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2001-07-09 14:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-09 14:16 Nathan Sidwell [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-09 14:46 c++/3336 Travis Smith 2001-07-09 14:36 c++/3336 Phil Edwards 2001-07-09 14:26 c++/3336 Travis Smith 2001-07-09 7:36 c++/3336 Travis Smith
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=20010709211604.22326.qmail@sourceware.cygnus.com \ --to=nathan@codesourcery.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: linkBe 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).