From: Greg KH <greg@kroah.com>
To: "xosé vázquez pérez" <xose@wanadoo.es>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [proposition of drivers documentation]
Date: Fri, 25 Apr 2003 11:58:32 -0700 [thread overview]
Message-ID: <20030425185832.GA3543@kroah.com> (raw)
In-Reply-To: <3EA96F27.3090207@wanadoo.es>
On Fri, Apr 25, 2003 at 07:23:51PM +0200, xosé vázquez pérez wrote:
> =CHANGELOG
>
> [Changelog]: (latest at top)
>
> [date] [version] or [modification #] [<e-mail@server.com>]
> - bug fixes at makemelove()
> ...
This starts to get very long over time, and quite messy, and pretty much
is pointless. I used to do it for my drivers, but have given up due to
no one ever reading it, and the advent of bitkeeper (you can get
individual revision history for every file now quite easily.)
> =HARDWARE
>
> [Supported hardware]:
>
> [manufacturer_1]
> [product name]
>
> [manufacturer_2]
> [product name]
>
> =END
This is already listed in the MODULE_DEVICE_TABLE and can be parsed
later by userspace tools quite easily.
thanks,
greg k-h
prev parent reply other threads:[~2003-04-25 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 17:23 [proposition of drivers documentation] xosé vázquez pérez
2003-04-25 18:58 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030425185832.GA3543@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xose@wanadoo.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox