public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Mike Stump <mrs@apple.com>
Cc: Biagio Lucini <lucini@phys.ethz.ch>,
	gcc@gcc.gnu.org, gomp@nongnu.org,  gcc-patches@gcc.gnu.org
Subject: Re: OpenMP licensing problem: a solution
Date: Wed, 24 Nov 2004 05:35:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.60.0411232100220.29669@dberlin.org> (raw)
In-Reply-To: <D8E4A4C4-FBE9-4C2F-BD67-53F18926050D@apple.com>



On Tue, 23 Nov 2004, Mike Stump wrote:

> On Nov 23, 2004, at 4:47 PM, Daniel Berlin wrote:
>> On Tue, 23 Nov 2004, Mike Stump wrote:
>> In this case, what you've said isn't necessarily or even usually true.
>
> I wasn't giving general advice of what we might be able to get away with or 
> what the law might allow for, but rather, a very conservative view that 
> hopefully doesn't fail to be conservative to keep us and them happy.

Sigh.
I believe you missed the point I was making, because i didn't bother to 
actually write it out. :)

The point is that you've stated a possible suggestion based upon an 
assumption of  law that may or may not be true (in this case it isn't, 
at least in the US).
The correct thing in these situations is to *always* bump it to a lawyer 
(in this case, the FSF lawyers), not try to figure out whether a given 
answer may be acceptable, and if you don't get an acceptable answer, bump 
it to a lawyer, for two reasons:

1. What is really an acceptable answer based on the law may not  be the 
same as what you think it is :). (While it may turn out often that what a 
lawyer will accept is a lot more conservative than what you've come up 
with, this isn't always the case).


2. Even if you had the "lawyers acceptable answer", you aren't the one who 
can do anything with it, only the FSF/SC (or someone who officially 
represents GCC) can.

  reply	other threads:[~2004-11-24  2:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  9:31 Biagio Lucini
2004-11-24  0:03 ` Mike Stump
2004-11-24  1:03   ` Daniel Berlin
2004-11-24  2:09     ` Joe Buck
2004-11-24  3:20     ` Mike Stump
2004-11-24  5:35       ` Daniel Berlin [this message]
2004-11-24  7:52         ` Joe Buck

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=Pine.LNX.4.60.0411232100220.29669@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gomp@nongnu.org \
    --cc=lucini@phys.ethz.ch \
    --cc=mrs@apple.com \
    /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).