public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [CFT/PATCH] give sound/oss/trident a holiday cleanup for 2.6
Date: Thu, 1 Jan 2004 16:26:43 -0800	[thread overview]
Message-ID: <20040101162643.579af2bf.akpm@osdl.org> (raw)
In-Reply-To: <20040102001203.GD1718@actcom.co.il>

Muli Ben-Yehuda <mulix@mulix.org> wrote:
>
> On Thu, Jan 01, 2004 at 04:04:20PM -0800, Andrew Morton wrote:
> 
> > hmm, how come a whitespace cleanup patch adds nearly 200 lines which have
> > trailing whitespace?
> 
> That would be either xemacs's or indent's fault. Can't be my
> fault. No sir. Anyway, unless whitespace-mode is lying to me now, no
> line has more than at most one character of whitespace added. If it
> bugs you, I'll clean it up - it's a slow night tonight ;-) 

Nah, leave it as is.  I'm just having a little whine.  I added a nifty
trailing-whitespace-detector to patch-scripts a while back and it's telling
me that a *lot* of people use broken editors.

> > Could we please have a description of the substantive changes in
> > this patch?
> 
> Sure thing: 

Thanks.



  reply	other threads:[~2004-01-02  0:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 18:38 [CFT/PATCH] give sound/oss/trident a holiday cleanup for 2.6 Muli Ben-Yehuda
2003-12-29 18:50 ` Linus Torvalds
2003-12-29 18:56   ` Muli Ben-Yehuda
2003-12-29 19:09     ` Jeff Garzik
2003-12-29 19:40       ` Linus Torvalds
2003-12-29 20:32         ` Jeff Garzik
2004-01-01 23:51   ` Muli Ben-Yehuda
2004-01-02  0:04     ` Andrew Morton
2004-01-02  0:12       ` Muli Ben-Yehuda
2004-01-02  0:26         ` Andrew Morton [this message]
2004-01-02  0:39           ` Mike Fedyk
2004-01-02  0:43             ` Andrew Morton
2003-12-29 18:53 ` Mike Fedyk

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=20040101162643.579af2bf.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.org \
    --cc=torvalds@osdl.org \
    /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