Re: Okay to commit purely cosmetic (indendation) fixes?

[Clive Tovero <clive.tovero@aol.com>]

> In that case, please start with CONTRIBUTE in the top-level directory
> of the Emacs source tree.
> 

I actually started yesterday higher-up, with "GNU *Coding Standards*" 
here: https://www.gnu.org/prep/standards/standards.html  It does address 
some of the software dev standards and practices of GNU in general.

The ./CONTRIBUTE file pointed to ./admin/notes, so I thought this file 
might be patched with the white space wisdom (including the underlying 
rationale, e.g. git blame issues):

./admin/notes/git-workflow

Git blame does have the -w option to ignore whitespace, but I haven't 
had to use git blame.  In general, I use a graphical tool called 
Meld--because the complexity of diffing overwhelms the symbolic part of 
my brain and I have to use more of the visual part.

I realized too, that this whole topic makes a good case for, in any 
project, picking an indentation style, maybe enforcing it in commits, 
and sticking with it.