From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262623AbVFXGtW (ORCPT ); Fri, 24 Jun 2005 02:49:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261243AbVFXGtW (ORCPT ); Fri, 24 Jun 2005 02:49:22 -0400 Received: from 167.imtp.Ilyichevsk.Odessa.UA ([195.66.192.167]:58580 "HELO port.imtp.ilyichevsk.odessa.ua") by vger.kernel.org with SMTP id S262623AbVFXGtR (ORCPT ); Fri, 24 Jun 2005 02:49:17 -0400 From: Denis Vlasenko To: Linus Torvalds , Jeff Garzik Subject: Re: [git patch] urgent e1000 fix Date: Fri, 24 Jun 2005 09:49:05 +0300 User-Agent: KMail/1.5.4 Cc: David Lang , Andrew Morton , Linux Kernel , Netdev List References: <42BA7FB5.5020804@pobox.com> <42BB4172.5000904@pobox.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506240949.05620.vda@ilport.com.ua> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Friday 24 June 2005 02:33, Linus Torvalds wrote: > To actually allow real fuzz or to allow real whitespace differences in the > patch data itself is a _much_ bigger issue than this trivial patch > corruption, and I'd prefer to avoid going there if at all possible. How about automatic stripping of _trailing_ whitespace on all incoming patches? IIRC no file type (C, sh, Makefile, you name it) depends on conservation of it, thus it's 100% safe. -- vda