This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Update^5: Fix PR other/44034
- From: Joern Rennecke <amylaar at spamcop dot net>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Gerald Pfeifer <gerald at pfeifer dot com>, Richard Guenther <richard dot guenther at gmail dot com>, bonzini at gnu dot org, dj at redhat dot com, neroden at gcc dot gnu dot org, aoliva at redhat dot com, Mark Mitchell <mark at codesourcery dot com>
- Date: Thu, 17 Jun 2010 11:41:59 -0400
- Subject: Re: Update^5: Fix PR other/44034
- References: <20100526035246.h4v4fkajq8kcs0wk-nzlynne@webmail.spamcop.net> <Pine.LNX.4.64.1005261121220.6834@digraph.polyomino.org.uk> <20100526074705.ybxjn3la80cwkgg4-nzlynne@webmail.spamcop.net> <20100526114501.naowcook48wo0kwg-nzlynne@webmail.spamcop.net> <20100528121743.sj8wuutpdwo8ggkc-nzlynne@webmail.spamcop.net> <20100607181903.vsr8r9994w8sk4o0-nzlynne@webmail.spamcop.net> <20100608230324.rh3qk1dp9usgswsg-nzlynne@webmail.spamcop.net> <Pine.LNX.4.64.1006171435170.19040@digraph.polyomino.org.uk>
Quoting "Joseph S. Myers" <joseph@codesourcery.com>:
Is there any reason I shouldn't review this patch, from a doc maintainer
perspective (it will also need build-system and middle-end reviews), while
waiting for the FSF to produce a better solution that (a) doesn't require
generated files to be checked in and (b) allows both existing and new hook
documentation to use the same system (by allowing existing hook
documentation, presently only GPL or only GFDL to go in the new target.def
and the generated tm.texi)? ((b) is much more important than (a) here, in
my view.)
For (b), it would be sufficent if the FSF gave us permission to distribute
the GFDLed target hook documentation under the GPL, and the
target hook declarations and their comments under the GFDL.
This might be slightly easier if the patch was installed first, because then
we can present the FSF with two a fixed bodies of text that we want to
distribute under GPL & GFDL.
As long as hooks get added the old way with separate GPLed code and
(usually flawed) GFDLed documentation (or without documentation), the
amount of text that needs relicensing keeps growing.