This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GFDL/GPL issues
- From: "Alfred M. Szmidt" <ams at gnu dot org>
- To: Paolo Bonzini <bonzini at gnu dot org>
- Cc: Joe dot Buck at synopsys dot COM, bkoz at redhat dot com, paul_koning at Dell dot com, kenner at vlsi1 dot ultra dot nyu dot edu, dnovillo at google dot com, dewar at adacore dot com, gcc at gcc dot gnu dot org, iant at google dot com, mark at codesourcery dot com, richard dot guenther at gmail dot com, stevenb dot gcc at gmail dot com
- Date: Wed, 04 Aug 2010 14:48:30 -0400
- Subject: Re: GFDL/GPL issues
- References: <4C5195FA.2060208@codesourcery.com> <4C52B176.7040807@adacore.com> <4C52E1C0.6090400@codesourcery.com> <4C53696B.7030801@adacore.com> <4C536B50.4010402@codesourcery.com> <AANLkTikQ_ajAfJu8LkCjCP_tVBmZOkNgXFNmFHAMzTiY@mail.gmail.com> <11008022317.AA08984@vlsi1.ultra.nyu.edu> <E5A51D93-66B1-40E1-8431-34F8F11E5E6D@dell.com> <20100803162022.GU17485@synopsys.com> <20100804002105.744fb6af@shotwell> <20100804164618.GX17485@synopsys.com> <E1Oghrf-0001JK-3B@fencepost.gnu.org> <4C59B33A.207@gnu.org>
- Reply-to: ams at gnu dot org
You probably haven't read this thread fully, or you wouldn't imply
that GCC should have an "options manual" separate from the user's
manual.
I have read the thread in full, and I do not see the problem with
keeping that info in a seperate manual; GCC has so many options for
various architectures and systems that I think it makes technical
sense to have a "Invoking GCC" manual.