public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: dewar@adacore.com, fw@deneb.enyo.de, bonzini@gnu.org,
		Joe.Buck@synopsys.com, gcc@gcc.gnu.org
Subject: Re: Compiling programs licensed under the GPL version 2 with GCC 4.4
Date: Mon, 27 Jul 2009 11:05:00 -0000	[thread overview]
Message-ID: <E1MVO1L-0004Yd-L6@fencepost.gnu.org> (raw)
In-Reply-To: <6c33472e0907270328u7b7a4edbo8291ff7afdf5e44c@mail.gmail.com> 	(message from =?ISO-8859-1?Q?Manuel_L=F3pez=2DIb=E1=F1ez?= on Mon, 27 	Jul 2009 12:28:10 +0200)

   > a) discussions of licensing issues are off topic on this mailing list
   >
   > b) you should ignore all such discussions, since they invariablly
   >   include lots of legal-sounding opinions from people who are not
   >   lawyers and don't know, and often have significant misconceptions.
   >
   > c) remember that even lawyers don't know what the exactly implications
   >   of copyright law are, juries often surprise. So even if you go ask
   >   a lawyer, you won't get a definitive opinion.

   These three points could be included in a standard answer to
   licensing questions posted to gcc@. Invariably, all such threads
   are a waste of time and bandwidth. Perhaps we can include the
   standard answer in some webpage so we can copy+paste or just point
   to it. A first attempt at: http://gcc.gnu.org/wiki/Licensing

The effort is laudable, but the above text has a negative sounding
tone.  It doesn't point users in the right direction.

How about the following wording,

  The most common questions and answers regarding the GNU GPL and how
  it applies can be found in the GNU GPL FAQ
  <http://gnu.org/licenses/gpl-faq.html>, if you cannot find the
  answer there please contact <legal@gnu.org> instead of posting your
  question on one of the GCC mailing-lists.

  reply	other threads:[~2009-07-27 11:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 20:53 Florian Weimer
2009-07-26  1:57 ` Joe Buck
2009-07-26  6:47   ` Florian Weimer
2009-07-26  9:38     ` Arnaud Charlet
2009-07-26  9:51       ` Florian Weimer
2009-07-26  9:56         ` Arnaud Charlet
2009-07-26 10:19           ` Florian Weimer
2009-07-26 21:51     ` Joe Buck
2009-07-27  6:10       ` Florian Weimer
2009-07-27  7:08         ` Paolo Bonzini
2009-07-27  9:35           ` Florian Weimer
2009-07-27  9:41             ` Alfred M. Szmidt
2009-07-27 10:07             ` Robert Dewar
2009-07-27 10:10               ` Paolo Bonzini
2009-07-27 10:28               ` Manuel López-Ibáñez
2009-07-27 11:05                 ` Alfred M. Szmidt [this message]
2009-07-27 12:19                   ` Manuel López-Ibáñez
2009-07-27 10:38               ` Dave Korn
2009-07-27 12:12                 ` Robert Dewar
2009-07-27 11:02               ` Florian Weimer
2009-07-27 12:10                 ` Robert Dewar
2009-07-27 14:29                   ` Frank Ch. Eigler
2009-07-28  0:34                     ` Russ Allbery
2009-07-28  0:57                       ` Joe Buck
2009-07-26  7:12   ` Vincent Lefevre
2009-07-27 21:47 ` Paolo Bonzini

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=E1MVO1L-0004Yd-L6@fencepost.gnu.org \
    --to=ams@gnu.org \
    --cc=Joe.Buck@synopsys.com \
    --cc=bonzini@gnu.org \
    --cc=dewar@adacore.com \
    --cc=fw@deneb.enyo.de \
    --cc=gcc@gcc.gnu.org \
    --cc=lopezibanez@gmail.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).