Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265640AbUATR47 (ORCPT ); Tue, 20 Jan 2004 12:56:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265641AbUATR47 (ORCPT ); Tue, 20 Jan 2004 12:56:59 -0500 Received: from fw.osdl.org ([65.172.181.6]:10454 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S265640AbUATR44 (ORCPT ); Tue, 20 Jan 2004 12:56:56 -0500 Date: Tue, 20 Jan 2004 09:56:41 -0800 (PST) From: Linus Torvalds To: Andries.Brouwer@cwi.nl cc: der.eremit@email.de, akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] fix for ide-scsi crash In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 32 On Tue, 20 Jan 2004 Andries.Brouwer@cwi.nl wrote: > > If Andries wants to > re-send the whitespace fixes, I can apply those too, but I hate applying > patches like this where the whitespace fixes hide the real fix. > > Yes, it seems we presently have no good mechanism / policy here. > Patches are noise. If some kernel version works and another doesnt, > one has to look at the diffs. Whitespace-only diffs are bad, > I would never submit them. They also needlessly invalidate existing patches. Whitespace-only diffs can be very useful. In particular, they are common when somebody starts working on a piece of code without a maintainer, and the old code was terminally broken wrt whitespace. Happens quite often in the driver world. So I don't have any real issues with applying whitespace-only patches, and I much prefer them to patches that mix whitespace and bugfixes. In particular, if the whitespace fixes are preparation for some other cleanup, it's usually a good idea. (I agree that if the whitespace fix is just random, it's usually not worth it). Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/