Date: Fri, 30 Nov 2012 07:41:05 -0500 From: Eitan Adler <eadler@freebsd.org> To: David Chisnall <theraven@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Bruce Evans <brde@optusnet.com.au> Subject: Re: svn commit: r243670 - head/share/man/man5 Message-ID: <CAF6rxgn%2BBObJ8CT4DpJYCQcBdsm2vYm0FmFAfsGhXSUjExB3SQ@mail.gmail.com> In-Reply-To: <4DDE660C-B809-47A5-AEBD-026FAAE8DB8B@FreeBSD.org> References: <201211291251.qATCpA7w078277@svn.freebsd.org> <20121130110154.E1441@besplex.bde.org> <CAF6rxgkUVrWbOU2i2=16St1iyWJskeULpWjDT5hEZi0aX%2BsHCQ@mail.gmail.com> <4DDE660C-B809-47A5-AEBD-026FAAE8DB8B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 November 2012 04:12, David Chisnall <theraven@freebsd.org> wrote: > On 30 Nov 2012, at 00:15, Eitan Adler wrote: > >> Every time I talk to the clang folk about flags they point me to gcc >> documentation. > > No we don't. We point you at the gcc documentation and at the clang manu= al. Clang aims to support all of the gcc flags, and provides some extra on= es as documented here: Actually, every time I've asked the response I got has been exactly "man gc= c" > If you are interested in writing a full manual for clang including the gc= c options, then that would almost certainly be appreciated. Most of this c= an be automatically generated. The best thing to do would be to write a ta= blegen back end that could emit mandoc from the existing options descriptio= ns. and then they mention this. I've thought about working on it, but ENOTIME usually ;) --=20 Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgn%2BBObJ8CT4DpJYCQcBdsm2vYm0FmFAfsGhXSUjExB3SQ>