Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753745AbZLRQ7l (ORCPT ); Fri, 18 Dec 2009 11:59:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753572AbZLRQ7k (ORCPT ); Fri, 18 Dec 2009 11:59:40 -0500 Received: from acsinet11.oracle.com ([141.146.126.233]:58600 "EHLO acsinet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753510AbZLRQ7j (ORCPT ); Fri, 18 Dec 2009 11:59:39 -0500 Date: Fri, 18 Dec 2009 08:58:58 -0800 From: Randy Dunlap To: Alasdair G Kergon Cc: device-mapper development , Joe Perches , Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org, Paul Mundt , Mikulas Patocka , Andy Whitcroft , Andrew Morton , Linus Torvalds Subject: Re: [dm-devel] Re: [PATCH] scripts/checkpatch.pl: Change long line warning to 105 chars Message-Id: <20091218085858.029c5660.randy.dunlap@oracle.com> In-Reply-To: <20091218151241.GD9334@agk-dp.fab.redhat.com> References: <20091217061229.GD3946@linux-sh.org> <24653.1261110557@localhost> <1261113144.13734.317.camel@Joe-Laptop.home> <20091218151241.GD9334@agk-dp.fab.redhat.com> Organization: Oracle Linux Eng. X-Mailer: Sylpheed 2.7.1 (GTK+ 2.12.0; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Source-IP: acsmt356.oracle.com [141.146.40.156] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090201.4B2BB4DA.0036:SCFMA4539814,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1184 Lines: 31 On Fri, 18 Dec 2009 15:12:41 +0000 Alasdair G Kergon wrote: > On Fri, Dec 18, 2009 at 03:37:00PM +0100, Krzysztof Halasa wrote: > > Not sure if that's long enough (maybe it is). > > 132 looks like the next "natural" number. > > Well it's good that this thread has produced more examples where it's > reasonable and acceptable to exceed 80 characters. > > What do people feel about files where the policy is to place all the > parameters passed into a function on the same line, regardless of its > consequent length? Not good IMO. It's much easier to read something that is restricted in width than to have to scroll/pan side to side. (e.g., newspaper columns. Oops, what's a newspaper?) > (What kicked this all off was a patch Mikulas submitted containing many > long lines, one of which hits column 264. Personally, I dislike reading > code with lines that wrap, but using a 132-column terminal width is > fine.) --- ~Randy -- 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/