public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "M. R. Brown" <mrbrown@0xd6.org>
To: Wayne Scott <wscott@bitmover.com>
Cc: linux-kernel@vger.kernel.org, jmd@turbogeek.org
Subject: Re: Extraneous whitespace removal?
Date: Fri, 30 Nov 2001 07:16:58 -0600	[thread overview]
Message-ID: <20011130071658.A786@0xd6.org> (raw)
In-Reply-To: <20011129.094040.124092017.wscott@bitmover.com>
In-Reply-To: <20011129.094040.124092017.wscott@bitmover.com>

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

* Wayne Scott <wscott@bitmover.com> on Thu, Nov 29, 2001:

> 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.  You have touched
> a huge number of lines and people will have to walk a list of merge
> conflicts everywhere they have made local changes and pick their side.
> And anytime people do a whole series of the same edits over and over
> they will miss that real conflict in the middle and lose some
> important change.
> 

diff -w, diff -b, diff -B

M. R.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2001-11-30 13:17 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
2001-11-30 13:16 ` M. R. Brown [this message]
  -- 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=20011130071658.A786@0xd6.org \
    --to=mrbrown@0xd6.org \
    --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