From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Nomenclature of udev documentation
Date: Fri, 11 Feb 2005 01:11:48 +0000 [thread overview]
Message-ID: <20050211011148.GD26982@kroah.com> (raw)
In-Reply-To: <20050210.173601.29803807.christopher_culver@yahoo.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
A: No.
Q: Should I include quotations after my reply?
On Thu, Feb 10, 2005 at 06:58:15PM -0600, Christopher Culver wrote:
> Still, if there's no great obstacle to changing the file name, then it
> should be done just to have consistency with other applications. It
> isn't just a GNU thing, most open source applications follow this
> nomenclature. Why be different?
What program is breaking because of this? Who is possibly
inconvenienced from it?
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-02-11 1:11 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 [this message]
2005-02-11 1:56 ` Ken Brush
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=20050211011148.GD26982@kroah.com \
--to=greg@kroah.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.