From: Eli Zaretskii <eliz@gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: gdb@sourceware.org, dewar@adacore.com, b07584@freescale.com,
rgetz@blackfin.uclinux.org, jimb@codesourcery.com
Subject: Re: Posting from work/university addresses
Date: Mon, 06 Aug 2007 14:22:00 -0000 [thread overview]
Message-ID: <ufy2whhhd.fsf@gnu.org> (raw)
In-Reply-To: <m3hcncvk12.fsf@localhost.localdomain> (message from Ian Lance Taylor on 06 Aug 2007 07:02:01 -0700)
> Cc: gdb@sourceware.org, dewar@adacore.com, b07584@freescale.com,
> rgetz@blackfin.uclinux.org, jimb@codesourcery.com
> From: Ian Lance Taylor <iant@google.com>
> Date: 06 Aug 2007 07:02:01 -0700
>
> The reason we would like to block the disclaimers is that they impose
> a legal liability on us. The problematic disclaimers are the ones
> which say something along the lines of "If you are not the intended
> recipient you must not disseminate, copy .... We request that you
> notify COMPANYNAME immediately." The problem is that we can not obey
> those instructions, as we automatically archive the e-mail message and
> make it available for anybody in the world to see. Since we are
> violating the terms of the disclaimer, the sender has reasonable
> grounds to sue us. It is likely that the suit would not prevail in
> the end, as my understanding is that the disclaimers are unenforceable
> under U.S. law, but that does not matter since we are a volunteer
> organization with no means to defend ourselves. I think it is very
> unwise to leave ourselves open to this sort of legal liability. This
> is of course a personal issue for me since as one of the
> administrators of gcc.gnu.org/sourceware.org, and the owner of the
> domain name sourceware.org, I would be personally named in the
> lawsuit.
Thanks for the clarifications. Avoiding legal suits is a perfectly
valid reason, as far as I'm concerned.
next prev parent reply other threads:[~2007-08-06 14:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 8:14 Why does gdb implement 'next' command with a series of "vCont;s"? congli
2007-07-30 22:12 ` Posting from work/university addresses Jim Blandy
2007-07-31 0:08 ` Anmol P. Paralkar
2007-07-31 1:08 ` Christopher Faylor
2007-08-02 16:58 ` Robin Getz
2007-08-02 17:12 ` Robert Dewar
2007-08-02 17:42 ` Robin Getz
2007-08-02 18:09 ` Ian Lance Taylor
2007-08-04 17:36 ` Eric Weddington
2007-08-02 18:23 ` Jim Blandy
2007-08-02 18:34 ` Christopher Faylor
2007-08-03 12:05 ` Eli Zaretskii
2007-08-03 14:27 ` Christopher Faylor
2007-08-03 14:39 ` Ian Lance Taylor
2007-08-03 17:10 ` Eli Zaretskii
2007-08-03 23:11 ` Christopher Faylor
2007-08-04 8:41 ` Eli Zaretskii
2007-08-04 18:36 ` Ian Lance Taylor
2007-08-04 18:51 ` Eli Zaretskii
2007-08-05 0:03 ` Christopher Faylor
2007-08-05 3:51 ` Robin Getz
2007-08-05 5:07 ` Christopher Faylor
2007-08-05 12:03 ` Robert Dewar
2007-08-05 18:27 ` Christopher Faylor
2007-08-06 6:53 ` Eli Zaretskii
2007-08-06 14:04 ` Ian Lance Taylor
2007-08-06 14:22 ` Eli Zaretskii [this message]
2007-08-04 20:04 ` Bob Rossi
2007-08-05 0:06 ` Christopher Faylor
2007-08-05 1:58 ` Bob Rossi
2007-08-05 3:13 ` Eli Zaretskii
2007-08-05 4:33 ` Christopher Faylor
2007-08-06 14:07 ` Ian Lance Taylor
2007-07-31 7:59 ` Wenbo Yang
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=ufy2whhhd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=b07584@freescale.com \
--cc=dewar@adacore.com \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=jimb@codesourcery.com \
--cc=rgetz@blackfin.uclinux.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