From owner-freebsd-current  Mon Jan  5 21:25:10 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA02312
          for current-outgoing; Mon, 5 Jan 1998 21:25:10 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA02304
          for <current@FreeBSD.ORG>; Mon, 5 Jan 1998 21:25:03 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id VAA08302; Mon, 5 Jan 1998 21:24:38 -0800 (PST)
To: Bruce Evans <bde@zeta.org.au>
cc: andreas@klemm.gtn.com, current@FreeBSD.ORG
Subject: Re: LINT is missing examples for sio1-3 ? GENERIC does so 
In-reply-to: Your message of "Tue, 06 Jan 1998 12:15:21 +1100."
             <199801060115.MAA16752@godzilla.zeta.org.au> 
Date: Mon, 05 Jan 1998 21:24:38 -0800
Message-ID: <8298.884064278@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> No.  LINT is suppose to have the minimal number of entries to give an
> instance of each type.  Only a few bogus entries breake this rule (grep
> for [a-z]1).

But what about showing also different instance/flag combinations?  I
don't see how it hurts to do that as separate entries if the
alternative is to muddy a single entry to the point of confusion.

					Jordan