Date: Wed, 26 Nov 2008 23:43:23 +0200 From: Manolis Kiagias <manolis@FreeBSD.org> To: Marc Fonvieille <blackend@FreeBSD.org> Cc: Manolis Kiagias <manolis@FreeBSD.org>, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org, doc-committers@FreeBSD.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/geom chapter.sgml Message-ID: <492DC2FB.7000203@FreeBSD.org> In-Reply-To: <20081126200624.GA1030@gothic.blackend.org> References: <200811261221.mAQCLmx6077169@repoman.freebsd.org> <20081126200624.GA1030@gothic.blackend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc Fonvieille wrote: >> </acronym> >> | - levels.</para> >> | + and manipulate the various <acronym>RAID</acronym> levels.</para> >> | </listitem> >> > > Where's the problem here ^^^^ ? > I find this sort of changes many times in your commit. > All these changes were indispensable? > Whitespaces fix should be done when the code starts to be a mess with > long lines and/or an indentation difficult to read. > > Certainly not indispensable, but I thought the point behind a whitespace commit is to tidy things up, before it gets messy after more commits. I know we should generally avoid whitespace commits for CVS bloat, but I was not aware of any more specific policy.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?492DC2FB.7000203>