Date: Tue, 21 May 2019 09:09:52 -0700 From: John Baldwin <jhb@FreeBSD.org> To: rgrimes@freebsd.org, Warner Losh <imp@bsdimp.com> Cc: Yoshihiro Ota <ota@j.email.ne.jp>, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, Benedict Reuschling <bcr@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-stable@freebsd.org, svn-src-all <svn-src-all@freebsd.org>, svn-src-stable-12@freebsd.org, Bruce Evans <brde@optusnet.com.au>, Konstantin Belousov <kostikbel@gmail.com> Subject: Re: svn commit: r347951 - stable/12/lib/libc/stdlib Message-ID: <00fa30ef-a454-d658-d81f-74efbe1d0429@FreeBSD.org> In-Reply-To: <201905201734.x4KHY7wH074764@gndrsh.dnsmgr.net> References: <201905201734.x4KHY7wH074764@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/20/19 10:34 AM, Rodney W. Grimes wrote: >> On Sun, May 19, 2019 at 9:56 AM Yoshihiro Ota <ota@j.email.ne.jp> wrote: >> >>> I wonder if we can use a tool to confirm coding style like >>> clang-format or something else. >>> >> >> I don't know... it might be hard to do that inside a man page... > > Given the current tooling I concur, so we need .include <foo.[hc]> > for mandoc, and teach mandoc how to format example code which > is mostly knows how to do, or atleast there was lots of groff > code to do that. I would prefer this approach if at all possible. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00fa30ef-a454-d658-d81f-74efbe1d0429>