Re: [PATCH 1/2] War on whitespace: first, a bit of retreat.

"J. Bruce Fields" [off-list ref] writes:

The whitespace policy varies based on the project (and in some cases,
based on the file within that project).  It shouldn't vary from user to
user or repo to repo.  So the configuration variable mechanism seems a
poor match.  Would it be possible to use something like gitattributes
instead?  Then the whitespace policy would be associated with the
project itself, would automatically be propagated on clone, etc.

The use of gitattributes certainly sounds like a good way to
go.  A project like git may say "HT indent for C sources, SP
only for Python parts".

Having said that, I've added a few tests and merged the result
to 'next' already.  We can improve it to use attributes instead
while on 'next'.

And the git-apply side needs a matching adjustment.