Date: Tue, 23 Oct 2012 12:39:45 +0200 From: Erik Cederstrand <erik@cederstrand.dk> To: "Wojciech A. Koszek" <wkoszek@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: FreeBSD in Google Code-In 2012? You can help too! Message-ID: <6CEA942D-3663-41DC-A919-584F664C67D9@cederstrand.dk> In-Reply-To: <20121016101957.GB53800@FreeBSD.org> References: <20121016101957.GB53800@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Den 16/10/2012 kl. 12.19 skrev Wojciech A. Koszek <wkoszek@freebsd.org>: > (cross-posted message; please keep discussion on freebsd-hackers@) > > Those of you who have Wiki access, please spent 2 more minutes and submit > straight to Wiki: > > http://wiki.freebsd.org/GoogleCodeIn/2012Tasks There are lots of smallish tasks in the code-quality department: * Analyze and fix Clang Static Analyzer warnings * Analyze and fix compiler warnings to increase WARNS level * Write regression tests for src/tools/regression * Run include-what-you-use to clean up header inclusion * Verify bugs with patches I think they're too open-ended to enter in the wiki as-is, but I'd also like to not spam the wiki with lots of almost-identical tasks. What's the best way to suggest them for CodeIn? Erikhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6CEA942D-3663-41DC-A919-584F664C67D9>