public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/44032] internals documentation is not legally safe to use
Date: Tue, 22 Feb 2011 16:59:00 -0000	[thread overview]
Message-ID: <bug-44032-4-ipWHwYQgQA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44032-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44032

--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> 2011-02-22 16:33:34 UTC ---
Joern, since the GFDL says:

    If your document contains nontrivial examples of program code, we
    recommend releasing these examples in parallel under your choice of
    free software license, such as the GNU General Public License,
    to permit their use in free software.

it ought not be controversial to add a statement that examples of code in the
internals manual are also released under the GPL.  I'd advise preparing a patch
adding a statement to the effect that

You can redistribute and/or modify examples of program code in this manual
under the terms of the GNU General Public License as published by the Free
Software Foundation; either version 3, or (at your option) any later version.

and sending the patch to RMS for legal review as well as gcc-patches for
technical review.


       reply	other threads:[~2011-02-22 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44032-4@http.gcc.gnu.org/bugzilla/>
2011-02-22 16:59 ` jsm28 at gcc dot gnu.org [this message]
2021-04-21  6:09 ` egallager at gcc dot gnu.org
2021-06-01 22:59 ` egallager at gcc dot gnu.org
2021-06-02 10:36 ` redi at gcc dot gnu.org
2010-05-07 22:06 [Bug other/44032] New: " amylaar at gcc dot gnu dot org
2010-05-07 22:31 ` [Bug other/44032] " steven at gcc dot gnu dot org

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=bug-44032-4-ipWHwYQgQA@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).