From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: /proc key naming consistency
Date: 13 Feb 2002 12:07:05 -0800 [thread overview]
Message-ID: <a4eh19$lko$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020213030047.8B1FB2257B@www.webservicesolutions.com>
Followup to: <20020213030047.8B1FB2257B@www.webservicesolutions.com>
By author: Mark Swanson <swansma@yahoo.com>
In newsgroup: linux.dev.kernel
>
> Notice the space between "cpu" and "MHz", or "cpu" and "family" yet there is
> no space between "fdiv" and "bug" (_).
>
> The reason I think NOT using a space is a good idea because it makes life
> easier for developers parsing /proc entries. Specifically, Java developers
> could use /proc/cpuinfo as a property file, but the space in the 'key' breaks
> java.util.Properties.load().
>
When I and Dan Quinlan submitted the cleanup for this we used _
everywhere. Unfortunately some other people not just added keys with
spaces, but gracefully "corrected" our "mistakes"...
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-02-13 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 2:50 RFC: /proc key naming consistency Mark Swanson
2002-02-13 5:00 ` Cameron Simpson
2002-02-13 20:07 ` H. Peter Anvin [this message]
2002-02-13 20:52 ` Daniel Phillips
2002-02-13 21:04 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 23:31 Luke Burton
2002-02-14 12:19 ` Miquel van Smoorenburg
2002-02-14 12:25 ` Wichert Akkerman
2002-02-14 16:09 ` Vince Weaver
2002-02-14 19:02 ` ertzog
2002-02-14 16:12 ` Alexander Viro
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='a4eh19$lko$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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.