Date: Thu, 16 Feb 2006 17:20:28 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Giorgos Keramidas <keramida@FreeBSD.org> Cc: freebsd-doc@FreeBSD.org, marck@rinet.ru Subject: Re: Handbook whitespace cleanup Message-ID: <20060216172028.30848f45.trhodes@FreeBSD.org> In-Reply-To: <20060216134237.GB9575@flame.pc> References: <20060213152314.B14115@woozle.rinet.ru> <E964D72E-E07B-4CE7-88B1-BA1CCD87216D@submonkey.net> <20060216134237.GB9575@flame.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Feb 2006 15:42:37 +0200 Giorgos Keramidas <keramida@freebsd.org> wrote: > On 2006-02-13 12:56, Ceri Davies <ceri@submonkey.net> wrote: > >On 13 Feb 2006, at 12:25, Dmitry Morozovsky wrote: > >> Dear colleagues, > >> > >> I think at least largest chapters (e.g., 300+ lines with whitespace > >> changes) > >> should be cleaned up. Any objections (besides well-known issue > >> with screen > >> and programlisting contents where should be no tabs)? > > > > Sorry, I don't see the point. > > At the very least make sure that nobody has diffs in progress. > > This is not very easy. It isn't enough either. Large sweeps for > indentation, wrapping and whitespace may also invalidate the patches we > have in our bugs database; which, frankly, sucks even more than seeing > how Gnats tends to mutilate & do various ugly things with patch > whitespace already. > > I prefer small whitespace/indentation commits as followup commits to > content changes, or even as part of content rewrites/fixes. Or, like in src/, before a large amount of work is done on that particular piece of documentation. -- Tom Rhodes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060216172028.30848f45.trhodes>