public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: seebs@plethora.net (Peter Seebach)
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] __attribute__ ((packed)) doesn't work
Date: Wed, 22 Feb 2006 11:32:00 -0000	[thread overview]
Message-ID: <200602221129.k1MBT60d024646@guild.plethora.net> (raw)
In-Reply-To: Your message of "Wed, 22 Feb 2006 12:24:55 +0100."              <43FC4A07.3070704@zurich.ibm.com>

In message <43FC4A07.3070704@zurich.ibm.com>, Dirk Husemann writes:
>could you leave this part of the signature out? sending something to a 
>public mailing list cannot be considered confidential and some companies 
>have rather strict rules about receiving unsolicited confidential 
>material...

The problem here is conflicting legal standards.  There are sound legal
reasons to absolutely require that ALL outgoing mail have that disclaimer
in some countries.  I know, it sounds dumb.  "The law is an ass."
Both companies are making rational decisions given the variety of atrociously
stupid laws and court decisions on such issues.

-s

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-02-22 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 11:18 Siegmund, Thomas
2006-02-22 11:25 ` Dirk Husemann
2006-02-22 11:32   ` Peter Seebach [this message]
2006-02-22 12:04     ` Andrew Lunn
2006-02-22 23:25       ` [ECOS] My petty complaint about your signature Brett Delmage
2006-02-22 12:42 AW: [ECOS] __attribute__ ((packed)) doesn't work Siegmund, Thomas
2006-02-22 14:49 ` Andrew Lunn
2006-02-22 15:05 AW: " Siegmund, Thomas
2006-02-22 15:37 ` Andrew Lunn
2006-02-23 15:27 AW: " Siegmund, Thomas
2006-03-02 18:41 ` Andrew Lunn

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=200602221129.k1MBT60d024646@guild.plethora.net \
    --to=seebs@plethora.net \
    --cc=ecos-discuss@ecos.sourceware.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).