svn commit: r203758 - in head/sys: amd64/conf arm/conf i386/conf ia64/conf mips/conf pc98/conf powerpc/conf sparc64/conf sun4v/conf

[John Baldwin]

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 at freebsd.org>
> >             Andriy Gapon <avg at 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