From: Ken Brush <kbrush@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Nomenclature of udev documentation
Date: Fri, 11 Feb 2005 01:56:24 +0000 [thread overview]
Message-ID: <ef88c0e005021017564909c926@mail.gmail.com> (raw)
In-Reply-To: <20050210.173601.29803807.christopher_culver@yahoo.com>
On Thu, 10 Feb 2005 17:36:01 -0600 (CST), Christopher Culver
<christopher_culver@yahoo.com> wrote:
> Udev comes with a "ChangeLog" file. However, the contents of this file
> are a friendly summary of changes instead of the very specific and
> technical remarks usually contained in file of that name. According to
> the GNU tradition of documentation, now upheld by most Free Software
> project, this file would more appropriately be called NEWS. I request
> that the maintainers change the name of this file, since consistency
> is good.
>
Looks like a Changelog to me.
Usually the NEWS file doesn't list changes per user, but an overview of
features added and bugs fixed sans submitter.
Whereas, a Changelog shows bugs fixed and features added, by submitter.
-Ken
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-02-11 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 23:36 Nomenclature of udev documentation Christopher Culver
2005-02-11 0:52 ` Greg KH
2005-02-11 0:58 ` Christopher Culver
2005-02-11 1:11 ` Greg KH
2005-02-11 1:56 ` Ken Brush [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=ef88c0e005021017564909c926@mail.gmail.com \
--to=kbrush@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.