Date: Wed, 17 Feb 2010 11:50:16 -0500 From: John Baldwin <jhb@freebsd.org> To: ticso@cicely.de Cc: danfe@freebsd.org, src-committers@freebsd.org, svn-src-all@freebsd.org, avg@freebsd.org, attilio@freebsd.org, svn-src-head@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: svn commit: r203758 - in head/sys: amd64/conf arm/conf i386/conf ia64/conf mips/conf pc98/conf powerpc/conf sparc64/conf sun4v/conf Message-ID: <201002171150.16645.jhb@freebsd.org> In-Reply-To: <20100216133032.GH43625@cicely7.cicely.de> References: <20100210203519.GA44831@FreeBSD.org> <20100215.171425.646090028373155752.imp@bsdimp.com> <20100216133032.GH43625@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 16 February 2010 8:30:32 am Bernd Walter wrote: > On Mon, Feb 15, 2010 at 05:14:25PM -0700, M. Warner Losh wrote: > > In message: <4B79CE84.3060901@freebsd.org> > > Andriy Gapon <avg@FreeBSD.org> writes: > > : At least in the i386/amd64 kernel config files typically we have: > > : options<space><tab>OPTION > > : And it is the case for the quoted above amd64 context. > > > > That's the standard way to add options in all kernel config files, > > although there's pockets here and there which don't quite comply. > > Interesting - I wasn't aware of this, but it surely makes sense. There's a comment in sys/conf/NOTES: # # NOTES conventions and style guide: # # Large block comments should begin and end with a line containing only a # comment character. # # To describe a particular object, a block comment (if it exists) should # come first. Next should come device, options, and hints lines in that # order. All device and option lines must be described by a comment that # doesn't just expand the device or option name. Use only a concise # comment on the same line if possible. Very detailed descriptions of # devices and subsystems belong in man pages. # # A space followed by a tab separates 'options' from an option name. Two # spaces followed by a tab separate 'device' from a device name. Comments # after an option or device should use one space after the comment character. # To comment out a negative option that disables code and thus should not be # enabled for LINT builds, precede 'options' with "#!". # -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002171150.16645.jhb>