From: "Dima Sorkin" <dima.sorkin@gmail.com>
To: "Manish Agarwal, Noida" <MANISH.AGRL@hcl.in>
Cc: gcc-help@gcc.gnu.org
Subject: Re: help....
Date: Fri, 29 Dec 2006 10:04:00 -0000 [thread overview]
Message-ID: <e40293600612290204l1a71f51u78913e11fc36195a@mail.gmail.com> (raw)
In-Reply-To: <A93BD15112CD05479B1CD204F7F1D47301992DAC@exch-04.noida.hcltech.com>
Hi.
Here references about "evil" disclaimers (as usual :).
Maybe other people on the list already got rid, but you may try
without a disclaimer.
http://gcc.gnu.org/ml/gcc-help/2006-11/msg00158.html
http://gcc.gnu.org/ml/gcc-help/2006-11/msg00161.html
http://gcc.gnu.org/ml/gcc-help/2006-12/msg00214.html
Regards,
Dima.
On 12/22/06, Manish Agarwal, Noida wrote:
> DISCLAIMER:
> -----------------------------------------------------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
> It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
> this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
> Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
> this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
> received this email in error please delete it and notify the sender immediately. Before opening any mail and
> attachments please check them for viruses and defect.
> -----------------------------------------------------------------------------------------------------------------------
>
next prev parent reply other threads:[~2006-12-29 10:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 9:37 help Manish Agarwal, Noida
2006-12-27 14:48 ` help manish manish
2006-12-29 10:04 ` Dima Sorkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-26 18:25 Help Lusine Avetisyan
2023-10-18 21:36 Help Peter Bergner
2023-06-12 2:58 help Jerry Lin
2005-03-28 14:42 Help umesh s
2004-08-30 12:46 Help help
2004-08-30 12:46 Help help
2002-04-16 4:50 Help zoushuo82
[not found] <616BE6A276E3714788D2AC35C40CD18D394681@whale.softwire.co.uk>
2002-02-01 1:11 ` Help Rupert Wood
2002-02-01 1:02 Help Aravind K Umesh
2002-02-01 7:48 ` Help Andrea 'Fyre Wyzard' Bocci
2002-01-30 1:41 help Aravind K Umesh
2002-01-16 5:02 Help Aravind K Umesh
2002-01-10 5:15 Help Sanjiv Kumar Gupta
2002-01-10 1:37 Help Aravind K Umesh
2002-01-07 1:22 Help Aravind K Umesh
2002-01-07 9:09 ` Help Andrea 'Fyre Wyzard' Bocci
2001-05-10 8:20 help Ripper
2001-05-10 17:50 ` help Alexandre Oliva
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=e40293600612290204l1a71f51u78913e11fc36195a@mail.gmail.com \
--to=dima.sorkin@gmail.com \
--cc=MANISH.AGRL@hcl.in \
--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).