Date: Thu, 28 May 2015 10:34:29 -0600 From: Alan Somers <asomers@freebsd.org> To: Allan Jude <allanjude@freebsd.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: Need help reducing compilation warnings in CURRENT Message-ID: <CAOtMX2iLfpAw4-6BTYmh2dWiBMpqnHwELjFDJfBGKz1XBH0iXA@mail.gmail.com> In-Reply-To: <556725BB.2040805@freebsd.org> References: <CAG=rPVdLjmj8oOeqQQOLr6ShvU=2H3y0j5hg4q8UrB70rj3Xpg@mail.gmail.com> <55670C5A.6080500@FreeBSD.org> <556725BB.2040805@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 28, 2015 at 8:27 AM, Allan Jude <allanjude@freebsd.org> wrote: > On 2015-05-28 08:38, Johannes Jost Meixner wrote: >> Hi Craig, >> >> I'll gladly help (good excuse to learn C), but looking at those errors >> in general, one thing pops out: >> >> The warnings are almost all in contrib/ areas. Hence, any fix might >> want to probably be submitted to upstream first. >> >> Correct me if I'm missing something obvious here please ;-) >> >> -J >> >> On 05/28/2015 09:30, Craig Rodrigues wrote: >>> Hi, >> >>> I've configured Jenkins to highlight compiler warnings and generate >>> a table. Jenkins also keeps track of new compiler warnings over >>> time. See: >> >>> https://jenkins.freebsd.org/job/FreeBSD_HEAD/warnings7 >> >>> Can anyone help improve the code by periodically looking at this >>> table and submitting patches to clean up the code? >> >>> Cleaning up compiler warnings is always boring work, but it is good >>> to clean up the code over time. >> >>> -- Craig _______________________________________________ >> > > Johannes has a point, it probably makes sense to exclude contrib/ and > cddl/ from the warnings tracking. I agree about contrib. But don't exclude all of cddl/, just exclude cddl/contrib. -Alan with one l > > -- > Allan Jude >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2iLfpAw4-6BTYmh2dWiBMpqnHwELjFDJfBGKz1XBH0iXA>