From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] segmentation fault running kismet
Date: Fri, 8 Feb 2008 08:08:02 +0100 [thread overview]
Message-ID: <005301c86a21$f1065c10$c503760a@atmel.com> (raw)
In-Reply-To: A1286843C9B74E46B0063D92B7844C280380FC65@azindbaex01.aztec.soft
>
> Joe et al.,
> Please help him and ignore the disclaimer.
> Neither Saurav nor I can help remove it from the mailer.
>
> And to top it, we don't have permission to access to external
> (un-official) mail servers; therefore we cannot help but send
> mails/requests from official id.
>
> Sorry for the inconvenience caused.
>
> Thanks & Regards,
> yogesh
>
The mailing list IS disclosing and distributing the mail.
You can add a disclaimer in your signature
saying that the comment below is not applicable to
any mail sent to an public mailing list!
Otherwise you should not be sending mails to mailing lists.
Best Regards
Ulf Samuelsson
>
> -----Original Message-----
> From: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org]
> On Behalf Of Joe
> Sent: Thursday, February 07, 2008 10:46 PM
> To: Saurav Kumar Barik
> Cc: buildroot at uclibc.org
> Subject: Re: [Buildroot] segmentation fault running kismet
>
>
> Do you really want an answer? So get rid of this. Some other MLs would
> have you banned on the spot.
>
>> This email message and its attachments may contain CONFIDENTIAL AND
>> PRIVILEGED INFORMATION intended for the sole use of the addressee(s).
>> If you have received it in error, please contact the sender by return
>> email, notify your system manager and destroy the original message and
>
>> any copies thereof. Any review, use, disclosure or distribution is
>> unlawful. Please check this email and any attachments for the presence
>
>> of viruses. The Company accepts no liability for any damage caused by
>
>> any virus transmitted by this email. The views or opinions presented
>> in this e-mail are solely those of the author and do not necessarily
>> represent those of the company. The Company reserves the right to
>> monitor, review and store the content of all messages sent to or from
>> this e-mail address.
>
> Greetz Joe
>
> --
> Sepp "ZaP" Holzmayr
>
> please reply to: zentrale.at.work at gmail.com
> "Never underestimate the bandwidth of a freight train full of DAT tapes.
>
> Only the round-trip is a little suboptimal."
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot
>
> This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.
> The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address.
>
> www.aztecsoft.com
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2008-02-08 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 16:31 [Buildroot] segmentation fault running kismet Saurav Kumar Barik
2008-02-07 17:16 ` Joe
2008-02-08 5:05 ` Yogesh Kumar Sharma
2008-02-08 7:08 ` Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 6:51 saurav barik
2008-02-08 8:08 ` Joe
2008-02-08 8:51 ` saurav barik
2008-02-12 7:04 ` saurav barik
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='005301c86a21$f1065c10$c503760a@atmel.com' \
--to=ulf@atmel.com \
--cc=buildroot@busybox.net \
/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