Re: removing white space highlight

[<tomas@tuxteam.de>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Feb 21, 2016 at 04:31:01AM +0100, Emanuel Berg wrote:

[...]

> Yes, so why not have it automatized once and for all
> and then never have to think about it?

Because it's a very rude thing to do when working with others?

If a (biggish) project has "whitespace issues", the sensible way of
doing it is:

 - agree that it's an issue. Otherwise *do nothing*. Introducing
   whitespace diffs at this stage "because I thing it's the right
   thing, dammit" is arrogant and unpolite -- and might result
   on being scolded. Rightfully so.

 - agree on a strategy. It could be "whenever a file is touched
   for whatever reason (a) or in a orchestrated series of commits (b)

 - in case (a) it's still meaningful to dedicate one commit to
   the whitespace change itself

 - in case (b) it'd make sense to agree on some time frame.

Of course, this wouldn't apply on a "clean" slate, where such
tools are definitely a plus. Still I'd prefer an indication to
a silent fix -- when fixing whitespaces in other's code, I'd
*always* ask first.

Working with others has its price.

- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlbJpB4ACgkQBcgs9XrR2kaBKgCdEaQSE3VEzPr2c2IZV0ilA2pj
+IoAn1NhPsvuKKR6GIWTLJ3obYUYLWwT
=RiPF
-----END PGP SIGNATURE-----