From owner-svn-src-all@FreeBSD.ORG Sun Mar 16 23:14:19 2014 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 773F689E; Sun, 16 Mar 2014 23:14:19 +0000 (UTC) Received: from mail107.syd.optusnet.com.au (mail107.syd.optusnet.com.au [211.29.132.53]) by mx1.freebsd.org (Postfix) with ESMTP id 35C7CF52; Sun, 16 Mar 2014 23:14:18 +0000 (UTC) Received: from c122-106-147-133.carlnfd1.nsw.optusnet.com.au (c122-106-147-133.carlnfd1.nsw.optusnet.com.au [122.106.147.133]) by mail107.syd.optusnet.com.au (Postfix) with ESMTPS id 755E7D44B3F; Mon, 17 Mar 2014 10:14:17 +1100 (EST) Date: Mon, 17 Mar 2014 10:14:14 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Warner Losh Subject: Re: svn commit: r263246 - in head/sys: amd64/conf i386/conf In-Reply-To: <201403161522.s2GFMrBD025427@svn.freebsd.org> Message-ID: <20140317100304.Q1131@besplex.bde.org> References: <201403161522.s2GFMrBD025427@svn.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=fbeUlSgF c=1 sm=1 tr=0 a=7NqvjVvQucbO2RlWB8PEog==:117 a=PO7r1zJSAAAA:8 a=7CtZVUGXL_QA:10 a=kj9zAlcOel0A:10 a=JzwRw_2MAAAA:8 a=zKlxM0aeT84R1zlGm0AA:9 a=CjuIK1q_8ugA:10 Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2014 23:14:19 -0000 On Sun, 16 Mar 2014, Warner Losh wrote: > Log: > Align all comments in config files on same column. This consistency > helps when bits and pieces of GENERIC from i386 or amd64 are cut and > pasted into other architecture's config files (which in the case of > ARM had gotten rather akimbo). Indentation of comments on device lines was not quite right, but this breaks the formatting further by blindly indenting without changing the comments, so that some lines are now too long. > Modified: head/sys/amd64/conf/GENERIC > ============================================================================== > --- head/sys/amd64/conf/GENERIC Sun Mar 16 15:22:46 2014 (r263245) > +++ head/sys/amd64/conf/GENERIC Sun Mar 16 15:22:52 2014 (r263246) > @@ -70,7 +70,7 @@ options MAC # TrustedBSD MAC Framewor > options KDTRACE_FRAME # Ensure frames are compiled in > options KDTRACE_HOOKS # Kernel DTrace hooks > options DDB_CTF # Kernel ELF linker loads CTF data > -options INCLUDE_CONFIG_FILE # Include this file in kernel > +options INCLUDE_CONFIG_FILE # Include this file in kernel > > # Debugging support. Always need this: > options KDB # Enable kernel debugger support. Comments on options lines lived for longer with indentation to column 40, so they are mostly carefully written to be not too long. > @@ -100,253 +100,253 @@ device pci > device fdc > > # ATA controllers > -device ahci # AHCI-compatible SATA controllers > -device ata # Legacy ATA/SATA controllers > -options ATA_STATIC_ID # Static device numbering > -device mvs # Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA > -device siis # SiliconImage SiI3124/SiI3132/SiI3531 SATA > +device ahci # AHCI-compatible SATA controllers > +device ata # Legacy ATA/SATA controllers > +options ATA_STATIC_ID # Static device numbering > +device mvs # Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA > +device siis # SiliconImage SiI3124/SiI3132/SiI3531 SATA Too long by 3 or 4 characters (83 columns). Too long by 11 or 12 characters when quoting in mail adds a prefix. Too long by 11 or 12 characters when commenting out adds a prefix of '# ', although an uglier prefix of '#' doesn't cause the extra indentation. When globally reformatting device lines, they should be more carefully formatted with spaces, like options lines are, so that commenting them out works better. The best formatting for this seems to be 'device'. For options lines, we use 'options'. 2 spaces instead of 1 are needed after the keyword to reach the first tab stop. The density of device lines that were of length >= 72 is not very high, but there are so many device lines that it is painful just to read them all. Bruce