From: Padraig Brady <padraig@antefacto.com>
To: Wayne Scott <wscott@bitmover.com>, jmd@turbogeek.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Extraneous whitespace removal?
Date: Thu, 29 Nov 2001 16:02:18 +0000 [thread overview]
Message-ID: <3C065C0A.7050809@antefacto.com> (raw)
In-Reply-To: <20011129.094040.124092017.wscott@bitmover.com>
Wayne Scott wrote:
> From: Jeremy M. Dolan <jmd@turbogeek.org>
>
>>Pluses:
>> - clean up messy whitespace
>> - cut precious picoseconds off compile time
>> - cut kernel tree by 200k (+/- alot)
>>
>>Minuses:
>> - adds 3.8M bzip2 or 4.7M gzip to next diff
>>
>
> As someone who has spend a lot of time working on version control and
> file merging, let be tell you the big minus you missed.
>
> After this patch go into the Linux kernel, everyone who is maintaining
> a set of patches in parallel with the main kernel has a lot of extra
> work resolving the conflicts caused by this change.
Which is why 2.5.1 is the only time it can go in.
It would save 140K compressed (bz2) which kernel.org
would probably appreciate, but it's probably too late
already so the next best is always do it for subsequent patches.
Perhaps their should be a patch_pp script that does runs
both Lindent and strip_ws? Actually Alan Cox mentioned to
me that pine had a bug where it stripped whitespace at end
of lines :-) can't depend on that though.
Padraig.
next prev parent reply other threads:[~2001-11-29 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 14:40 Extraneous whitespace removal? Wayne Scott
2001-11-29 16:02 ` Padraig Brady [this message]
2001-11-30 13:16 ` M. R. Brown
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 10:42 Jeremy M. Dolan
2001-01-08 11:29 ` David Weinehall
2001-01-08 11:50 ` Thomas Pornin
2001-01-09 0:24 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C065C0A.7050809@antefacto.com \
--to=padraig@antefacto.com \
--cc=jmd@turbogeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wscott@bitmover.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox