"Randy.Dunlap" <rddunlap _at_ osdl.org> wrote: > > So please don't bother with just whitespace changes unless you > are going to cleanup a <driver | fs | module | etc> completely. And if you're going to do that, do the whitespace cleanup _first_, so the substantive changes to the driver/fs/module/etc can be sanely understood and reverted if necessary. I frequently sneakily remove all newly-added trailing whitespace from the patches people send me. In 15 years it'll all be gone. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: RFC: Trailing blanks in source filesjw schultz
- Re: RFC: Trailing blanks in source filesAndi Kleen
- Re: RFC: Trailing blanks in source filesJoseph D. Wagner
- Re: RFC: Trailing blanks in source filesDavid Weinehall
- Re: RFC: Trailing blanks in source filesRandy.Dunlap
- Prev by Date: Re: MO: opening for write in cdrom.c
- Next by Date: Re: [2.6.1] fbdev console: can't load vga=791 and yes vga=ask!
- Previous by thread: Re: RFC: Trailing blanks in source files
- Next by thread: Re: RFC: Trailing blanks in source files
- Indexes:[Main][Thread]