Date: Thu, 11 Nov 2004 18:42:38 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: "David O'Brien" <obrien@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/contrib/gcc gcc.1 Message-ID: <20041111164238.GA1063@orion.daedalusnetworks.priv> In-Reply-To: <20041111163517.GA56382@dragon.nuxi.com> References: <200411110745.iAB7j1tj085796@repoman.freebsd.org> <20041111144834.GA735@orion.daedalusnetworks.priv> <20041111163517.GA56382@dragon.nuxi.com>
index | next in thread | previous in thread | raw e-mail
On 2004-11-11 08:35, David O'Brien <obrien@freebsd.org> wrote: > > > 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. That would great! Converting existing text to mdoc is far better than extracting all the necessary bits from texinfo myself.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041111164238.GA1063>