Date: Mon, 15 Mar 2004 14:47:13 -0500 From: Thomas Dickey <dickey@radix.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Colin Percival <colin.percival@wadham.ox.ac.uk> Subject: Re: spaces before tabs Message-ID: <20040315194713.GA13467@saltmine.radix.net> In-Reply-To: <200403151853.i2FIrhJr062646@apollo.backplane.com> References: <6.0.1.1.1.20040314234126.03adbc50@imap.sfu.ca> <20040315162816.GB61147@dragon.nuxi.com> <6.0.1.1.1.20040315164047.03bd0ea8@imap.sfu.ca> <20040315174421.GA23596@saltmine.radix.net> <200403151853.i2FIrhJr062646@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 15, 2004 at 10:53:43AM -0800, Matthew Dillon wrote: > You guys are so funny. I'm probably the most liberal when it comes > to allowing formatting changes to source code, e.g. ANSIfication, > de-registerization, bracing and other syntactical changes... but even > I would not accept large scale patches which simply change spaces to > tabs or removes trailing whitespace. That's just plain silly. sure (best read with a good editor): #define this_is_misleading \=20 int this_is_not_part_of_the_previous_line; But it's my practice to compare object files before/after doing formatting changes (doesn't catch all of the problems, but is necessary). --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFAVgg/tIqByHxlDocRAhgIAJ9f1pIgII6/Vqxo5oFfeD8nyCFFfQCcDRhe SIDtAeXu0PiT1hwPaJqel9M= =ej5e -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040315194713.GA13467>