From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,1efdd369be089610
X-Google-Attributes: gid103376,public
X-Google-Thread: 1025b4,1d8ab55e71d08f3d
X-Google-Attributes: gid1025b4,public
From: rms@gnu.ai.mit.edu (Richard Stallman)
Subject: Re: what DOES the GPL really say?
Date: 1997/09/01
Message-ID: <5udro8$2so@psilocin.gnu.ai.mit.edu>#1/1
X-Deja-AN: 269332451
Organization: Project GNU
Newsgroups: comp.lang.ada,gnu.misc.discuss
Date: 1997-09-01T00:00:00+00:00
List-Id: <comp.lang.ada>


The GNU GPL was designed to achieve certain specific goals.  One goal
of the GPL was to ensure that if you have a copy of a GPL-covered
program, you have the freedom to redistribute it.  Another goal is
that if you get a modified version of a GPL-covered program, you get
the source code, or have a way of getting the source code.

Occasionally someone disobeys the GNU GPL.  If they do this with a
program whose copyright belongs to the FSF, the FSF can take action to
make them comply.  But in order to even consider doing this, we need a
precise description of the facts of what is occurring.  We need this
in order to determine whether the GPL is being violated, and also as
the basis for taking action if it is being violated.

When you encounter a bug in a program, if you want it to be fixed, the
way to get it fixed is by sending a precise bug report to the
maintainers.  If you complain to the public about the problem, without
reporting it properly to the maintainers, you should complain about
yourself, because you are the one failing to take constructive action.

It is the same with violations of the GPL.  In order for the author or
copyright holder to take action, you have to make a precise report of
the facts of what is happening.

I recently heard from an employee of Wind River Systems who wanted to
know how they could assign all their changes to the FSF.  This
suggests that they want their changes to be included in a subsequent
GDB release.  This doesn't necessarily mean we WANT to install their
changes; that depends on how much extra work this would make for GDB
maintenance in the future.  For the GNU project, supporting embedded
systems is a side issue.  But if it is not unduly burdensome to
include the changes, we surely would.

Whatever their future plans may be, Wind River Systems is obliged to
obey the GNU GPL when distributing GDB.  If you received a binary of a
modified version of GDB (or any GNU program) from Wind River (or from
anyone else), you should have also received either the complete source
code of the modified program, or a written offer to supply you with
that complete source code subsequently by mail order, valid for at
least three years, for a limited price as required by section 3 of the
GNU GPL.

If you did not get the source or a proper written offer to send the
source, please report the facts clearly and dispassionately to
gnu@prep.ai.mit.edu.