From owner-cvs-src@FreeBSD.ORG Thu Nov 11 16:42:44 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2399316A4CE; Thu, 11 Nov 2004 16:42:44 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33CD843D49; Thu, 11 Nov 2004 16:42:42 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iABGgd54028351; Thu, 11 Nov 2004 18:42:40 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iABGgckt002925; Thu, 11 Nov 2004 18:42:38 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost)iABGgcEF002924; Thu, 11 Nov 2004 18:42:38 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 11 Nov 2004 18:42:38 +0200 From: Giorgos Keramidas To: "David O'Brien" Message-ID: <20041111164238.GA1063@orion.daedalusnetworks.priv> References: <200411110745.iAB7j1tj085796@repoman.freebsd.org> <20041111144834.GA735@orion.daedalusnetworks.priv> <20041111163517.GA56382@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041111163517.GA56382@dragon.nuxi.com> cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/contrib/gcc gcc.1 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 16:42:44 -0000 On 2004-11-11 08:35, David O'Brien 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.