Date: Tue, 31 Mar 2015 08:03:37 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Kurt Jaeger <pi@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r382799 - head/mail/rainloop Message-ID: <20150331080336.GA137@FreeBSD.org> In-Reply-To: <20150331075119.GG1017@f10.opsec.eu> References: <201503310733.t2V7XuXK025802@svn.freebsd.org> <20150331074530.GA96248@FreeBSD.org> <20150331075119.GG1017@f10.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 31, 2015 at 09:51:19AM +0200, Kurt Jaeger wrote: > > On Tue, Mar 31, 2015 at 07:33:56AM +0000, Kurt Jaeger wrote: > > > New Revision: 382799 > > > URL: https://svnweb.freebsd.org/changeset/ports/382799 > > > > > > Log: > > > mail/rainloop: Add an OPTIONS_DEFAULT > > > > May I ask, why MYSQL was preferred over SQLITE? > > That's what the submitter provided. Submitter might provide whatever they want. It is the jobs of the committer to verify and assess suggested changes, ensure they are indeed warranted, adhere to out practices and quality standards, and *adequately explain* them in the commit log. A good rule of thumb is that commit log should 30% talk about _what_ was changed, with remaining 70% devoted to _why_ it was made. I know people are often get bored of writing long commit logs, but perhaps 100%:0% ratio in case of not-so-perfectly obvious change (like this one) is way off the course. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150331080336.GA137>