public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Santhosh1 C <santhosh1.c@tcs.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Help required to upgrade gcc
Date: Wed, 30 May 2007 01:09:00 -0000	[thread overview]
Message-ID: <m3tztv2keu.fsf@localhost.localdomain> (raw)
In-Reply-To: <OF4C614991.04B50B87-ON652572E9.0028937B-652572E9.0028938A@tcs.com>

Santhosh1 C <santhosh1.c@tcs.com> writes:

> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you

Please do not send messages with this sort of attachment to the gcc
mailing lists.  They are against list policy as described at
http://gcc.gnu.org/lists.html.  If these disclaimers are added
automatically and you can not turn them off, I recommend using a free
web based e-mail service such as the ones offered by Google or
Yahoo!.  Thanks.

Ian

  reply	other threads:[~2007-05-30  1:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28  9:37 Santhosh1 C
2007-05-30  1:09 ` Ian Lance Taylor [this message]
     [not found] <1207217294.28834.ezmlm@gcc.gnu.org>
2008-04-03 10:34 ` wp
2008-04-03 10:46   ` Ian Baker
2008-04-03 11:16   ` Rupert Wood
2008-04-03 12:31     ` Tom Browder
2008-04-03 18:49       ` wp
2008-04-03 21:06         ` Tom Browder

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=m3tztv2keu.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=santhosh1.c@tcs.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).