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/52207] License on gcc/doc/include/gcc-common.texi screws up the licenses of many other documents. Date: Sat, 11 Feb 2012 12:19:00 -0000 [thread overview] Message-ID: <bug-52207-4-b2IPE1qgWT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52207-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52207 Joseph S. Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gerald at pfeifer dot com --- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> 2012-02-11 12:18:48 UTC --- This is clearly a matter for the SC. I'd suggest they seek approval from the FSF to (a) put suitable terms directly on gcc-common.texi (maybe GFDL without invariant sections or cover texts, maybe permissive terms); (b) remove cover texts and invariant sections from manuals that are under 400 pages and not published on paper by the FSF, as per the policies at <http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Documentation.html> that do not require such cover texts and invariant sections in that case.
next prev parent reply other threads:[~2012-02-11 12:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-10 23:39 [Bug other/52207] New: " naesten at gmail dot com 2012-02-10 23:46 ` [Bug other/52207] " pinskia at gcc dot gnu.org 2012-02-11 12:19 ` jsm28 at gcc dot gnu.org [this message] 2012-02-13 18:54 ` naesten at gmail dot com 2012-02-13 21:08 ` steven at gcc dot gnu.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-52207-4-b2IPE1qgWT@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: linkBe 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).