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. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
