Date: Sun, 15 Mar 2015 18:40:05 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r381196 - head/converters/p5-Encode-JIS2K Message-ID: <20150315154004.GE18303@hades.panopticon> In-Reply-To: <20150314113758.GA93218@FreeBSD.org> References: <201503131326.t2DDQrUw087705@svn.freebsd.org> <20150313170805.GB12328@FreeBSD.org> <20150313231612.GD18303@hades.panopticon> <20150314113758.GA93218@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Alexey Dokuchaev (danfe@FreeBSD.org) wrote: > > > How feasible would it be to group this kind of similar commits together > > > (at least per-category)? > > > > Unfortunately, it won't. I do, test and commit these on individual basis. > > Doing and testing are certainly per-port thing; yet I do not see why > deferring commit (esp. given that changes are typically small and trivial) > is not possible. Commit corresponds to a single isolated change, which is a change to a single port. Artifically grouping them is pointless and evil, as it makes merges and reverts harder. Actually, it's just the coincidence that this serie had the same commit message. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150315154004.GE18303>