Date: Sun, 03 Jul 2005 01:19:11 -0000 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: Giorgos Keramidas <keramida@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, "David E. O'Brien" <obrien@freebsd.org> Subject: Re: cvs commit: src/contrib/gcc gcc.1 Message-ID: <20041111155844.GC3522@zaphod.nitro.dk> 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
[-- Attachment #1 --] On 2004.11.11 16:48:35 +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? I think it has been mentioned a few times in the past that the role as gcc(1) manual page maintainer/janitor is open :-). -- Simon L. Nielsen FreeBSD Security Team [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBk4w0h9pcDSc1mlERAvTVAKCgZP42FfT1BDLzQeNgY96HGofPaQCfa8C1 Wp0cfZ6tBYLlbZFZ76bGdqM= =RSMk -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041111155844.GC3522>