Date: Sun, 03 Jul 2005 01:16:01 -0000 From: "David O'Brien" <obrien@freebsd.org> To: Giorgos Keramidas <keramida@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/contrib/gcc gcc.1 Message-ID: <20041111163517.GA56382@dragon.nuxi.com> In-Reply-To: <20041111144834.GA735@orion.daedalusnetworks.priv> References: <200411110745.iAB7j1tj085796@repoman.freebsd.org> <20041111144834.GA735@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 11, 2004 at 04:48:35PM +0200, Giorgos Keramidas wrote: > On 2004-11-11 07:45, "David E. O'Brien" <obrien@freebsd.org> wrote: > > > > Don't attempt to claim what version of GCC we're documenting. The manpage > > is still mostly the GCC 2.95 one, with faint attempts by me over the years > > to document a few new switches. Thus, it is dubious to claim documentation > > of specific modern GCC versions. > > > > Noted by: delphij > > > > Revision Changes Path > > 1.20 +1 -1 src/contrib/gcc/gcc.1 > > Does it make sense to attempt writing an mdoc manpage for a more modern > version of gcc, using the info manuals as the source? That is one approach. We should maybe periodically (say when GCC is upgraded across major revisions) build the port of the same version, and just commit built man page.[*] It will be in ancient nroff, but at least it will be current. Maybe we could even write a script to wack it more into mandoc format. I can mail you the 3.4 port manpage to play with. -- -- David (obrien@FreeBSD.org) [*] the manpage is built from texinfo sources, using perl and Pod::Man.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041111163517.GA56382>