Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759755AbXHXLIM (ORCPT ); Fri, 24 Aug 2007 07:08:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755464AbXHXLH6 (ORCPT ); Fri, 24 Aug 2007 07:07:58 -0400 Received: from wr-out-0506.google.com ([64.233.184.238]:25097 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754334AbXHXLH5 (ORCPT ); Fri, 24 Aug 2007 07:07:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=sASLMT4kfA62tO2s+3VqbTWUlD8JCa8M7MF6fY8bZ0cobrLTcUclJEZvhTp03LD3w/0zddQgZr/vZUrGnrEsIGKa8tX2K3dmjhEVjAHNlyWifVuEumMXf7lJDG+JpYZeajSeUKahF1/qSQ43DxBvZNx3ht+SYzet1GWkgbRtvXs= Message-ID: <9a8748490708240407pf1fa935j2dae3b0c108b3231@mail.gmail.com> Date: Fri, 24 Aug 2007 13:07:54 +0200 From: "Jesper Juhl" To: "Alan Cox" Subject: Re: Ideas on column length in kernel "problem"? Cc: "Andi Drebes" , postfail@hushmail.com, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org In-Reply-To: <20070824114611.7b17cafd@the-village.bc.nu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_157465_32986189.1187953674736" References: <20070823035442.6FD0DDA81F@mailserver7.hushmail.com> <200708241231.52767.lists-receive@programmierforen.de> <20070824114611.7b17cafd@the-village.bc.nu> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3313 Lines: 72 ------=_Part_157465_32986189.1187953674736 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 24/08/07, Alan Cox wrote: > > I think this is also a matter of conding style. Documentation/CodingStyle > > says: > > > > "The limit on the length of lines is 80 columns and this is a hard limit." > > As has repeatedly been stated this is a bug in Documentation/CodingStyle > and bears no resemblence to reality. > So let's update CodingStyle once and for all so that doesn't pop up again. See attached patch (inline version is whitespace damaged - can't help it from my current location). As continuously gets pointed out, the 80 col line length defined in CodingStyle is not a hard limit in real life. Let the document reflect reality. Signed-off-by: Jesper Juhl --- --- Documentation/CodingStyle~ 2007-08-24 13:04:20.000000000 +0200 +++ Documentation/CodingStyle 2007-08-24 13:04:20.000000000 +0200 @@ -77,7 +77,8 @@ Coding style is all about readability and maintainability using commonly available tools. -The limit on the length of lines is 80 columns and this is a hard limit. +The limit on the length of lines is 80 columns. This is a soft limit, it can +be broken in some cases, but you should respect it whenever possible. Statements longer than 80 columns will be broken into sensible chunks. Descendants are always substantially shorter than the parent and are placed -- Jesper Juhl Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html ------=_Part_157465_32986189.1187953674736 Content-Type: application/octet-stream; name=line-length.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_f5qkvwvo Content-Disposition: attachment; filename="line-length.patch" CkFzIGNvbnRpbnVvdXNseSBnZXRzIHBvaW50ZWQgb3V0LCB0aGUgODAgY29sIGxpbmUgbGVuZ3Ro IGRlZmluZWQgaW4gQ29kaW5nU3R5bGUKaXMgbm90IGEgaGFyZCBsaW1pdCBpbiByZWFsIGxpZmUu IExldCB0aGUgZG9jdW1lbnQgcmVmbGVjdCByZWFsaXR5LgoKU2lnbmVkLW9mZi1ieTogSmVzcGVy IEp1aGwgPGplc3Blci5qdWhsQGdtYWlsLmNvbT4KLS0tCgotLS0gRG9jdW1lbnRhdGlvbi9Db2Rp bmdTdHlsZX4JMjAwNy0wOC0yNCAxMzowNDoyMC4wMDAwMDAwMDAgKzAyMDAKKysrIERvY3VtZW50 YXRpb24vQ29kaW5nU3R5bGUJMjAwNy0wOC0yNCAxMzowNDoyMC4wMDAwMDAwMDAgKzAyMDAKQEAg LTc3LDcgKzc3LDggQEAKIENvZGluZyBzdHlsZSBpcyBhbGwgYWJvdXQgcmVhZGFiaWxpdHkgYW5k IG1haW50YWluYWJpbGl0eSB1c2luZyBjb21tb25seQogYXZhaWxhYmxlIHRvb2xzLgogCi1UaGUg bGltaXQgb24gdGhlIGxlbmd0aCBvZiBsaW5lcyBpcyA4MCBjb2x1bW5zIGFuZCB0aGlzIGlzIGEg aGFyZCBsaW1pdC4KK1RoZSBsaW1pdCBvbiB0aGUgbGVuZ3RoIG9mIGxpbmVzIGlzIDgwIGNvbHVt bnMuIFRoaXMgaXMgYSBzb2Z0IGxpbWl0LCBpdCBjYW4KK2JlIGJyb2tlbiBpbiBzb21lIGNhc2Vz LCBidXQgeW91IHNob3VsZCByZXNwZWN0IGl0IHdoZW5ldmVyIHBvc3NpYmxlLgogCiBTdGF0ZW1l bnRzIGxvbmdlciB0aGFuIDgwIGNvbHVtbnMgd2lsbCBiZSBicm9rZW4gaW50byBzZW5zaWJsZSBj aHVua3MuCiBEZXNjZW5kYW50cyBhcmUgYWx3YXlzIHN1YnN0YW50aWFsbHkgc2hvcnRlciB0aGFu IHRoZSBwYXJlbnQgYW5kIGFyZSBwbGFjZWQK ------=_Part_157465_32986189.1187953674736-- - 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/