James Bottomley wrote:
quoted text
> 
> but there are many more.  The greatest problem, as I see it is that by
> pouring vitriol like this on newbies, we're really damaging our
> reputation as a community that welcomes newcomers and strangling our
> necessary supply of willing volunteers.  On the other hand, as a
> maintainer, when there's people yelling me at about patches not being
> included plus a persistent regressions list and about ten bug reports to
> track down, the last thing I want to see within a million miles of my
> inbox is a white space fixing patch.  The more of these patches we get,
> the worse the problem becomes and the shorter and more inflammatory the
> responses get. We can't go on like this.
> 

As far as whitespace fixes, it seems we should just declare a flag day, 
specifically, right before Linus releases 2.6.26 or .27 he'd run 
"cleanfile" on the WHOLE TREE and check it in (either as one patch or 
several.)

After that, one would either have to use "patch -l" to refresh patches 
across the flag day, or I would write a reverse version of "cleanpatch" 
(one which cleans the minus lines and the context instead of the output) 
to fix them up.

Then the whole tree would be whitespace-clean, it would concentrate the 
pain to a single event, and then we can go on with life.

	-hpa
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/