From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965509AbXDGIBF (ORCPT ); Sat, 7 Apr 2007 04:01:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965496AbXDGIBF (ORCPT ); Sat, 7 Apr 2007 04:01:05 -0400 Received: from fed1rmmtao107.cox.net ([68.230.241.39]:49462 "EHLO fed1rmmtao107.cox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965509AbXDGIBE (ORCPT ); Sat, 7 Apr 2007 04:01:04 -0400 From: Junio C Hamano To: David Brownell Subject: Re: coding style for long conditions References: <11757099691323-git-send-email-tony@atomide.com> <200704061557.12662.david-b@pacbell.net> <1175901682.28263.507.camel@localhost.localdomain> <200704061634.39344.david-b@pacbell.net> cc: tglx@linutronix.de, Stefan Richter , Jan Engelhardt , Randy Dunlap , Tony Lindgren , linux-kernel@vger.kernel.org Date: Sat, 07 Apr 2007 01:01:02 -0700 In-Reply-To: <200704061634.39344.david-b@pacbell.net> (David Brownell's message of "Fri, 6 Apr 2007 16:34:38 -0700") Message-ID: <7v8xd4fwap.fsf@assigned-by-dhcp.cox.net> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) 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 David Brownell writes: > So in practical terms "\n \t" and "\n\t" are identical; > although the former "should not" be used, it doesn't > actually affect what CodingStyle is primarily trying to > control (i.e. what the code looks like). That's not what CodingStyle is trying to control. Not "what the code looks like" at all. Think why this line is here at the end of Chapter 1. Get a decent editor and don't leave whitespace at the end of lines. By the way, "git show --color 0aa599c -- drivers/usb/net/usbnet.h" would catch this kind of breakage if you have git.