From: Muli Ben-Yehuda <mulix@mulix.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: [CFT/PATCH] give sound/oss/trident a holiday cleanup for 2.6
Date: Mon, 29 Dec 2003 20:56:27 +0200 [thread overview]
Message-ID: <20031229185627.GJ13481@actcom.co.il> (raw)
In-Reply-To: <Pine.LNX.4.58.0312291049020.2113@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Mon, Dec 29, 2003 at 10:50:46AM -0800, Linus Torvalds wrote:
> > - run the code through Lindent, and then fix it manually (this is the
> > bulk of the patch)
>
> When doing things like this, can you split up the patches into two
> separate things: one that _only_ does whitespace changes, and that is
> guaranteed not to change anything else, and another that does the
> rest.
You're 100% right. Internally, the patch I sent is composed of 30
different patches. The reason I didn't seperate it into two patches is
that the changes were interleaved and inter-dependant and seperating
them was a b*tch. If Andrew wishes to include it in -mm or you wish to
include it in -vanilla and would like it in two seperate patches, I'll
go back and redo it that way.
Thanks and cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/
"the nucleus of linux oscillates my world" - gccbot@#offtopic
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-29 18:58 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 [this message]
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
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=20031229185627.GJ13481@actcom.co.il \
--to=mulix@mulix.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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