From: Ian Lance Taylor <ian@airs.com>
To: Digvijoy Chatterjee <digvijoy_chatterjee@infosys.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC Error Referencing re_comp & re_exec
Date: Wed, 28 Sep 2005 03:20:00 -0000 [thread overview]
Message-ID: <m37jd16fpl.fsf@gossamer.airs.com> (raw)
In-Reply-To: <1127877004.4932.5.camel@localhost.localdomain>
Digvijoy Chatterjee <digvijoy_chatterjee@infosys.com> writes:
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
Please do not send e-mail with this sort of disclaimer to the gcc
mailing lists. They are against list policy, as described here:
http://gcc.gnu.org/lists.html
If you can not prevent your e-mail server from adding these
disclaimers, then we suggest using a free web based e-mail account.
Thanks.
Ian
prev parent reply other threads:[~2005-09-28 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 22:13 DimmerMI (sent by Nabble.com)
2005-09-27 22:21 ` Ian Lance Taylor
2005-09-28 3:05 ` Digvijoy Chatterjee
2005-09-28 3:20 ` Ian Lance Taylor [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=m37jd16fpl.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=digvijoy_chatterjee@infosys.com \
--cc=gcc-help@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).