From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Wireless Extension update
Date: 14 Oct 2001 17:07:53 -0700 [thread overview]
Message-ID: <9qd9cp$977$1@cesium.transmeta.com> (raw)
In-Reply-To: <3BC3243A.D3B48880@osdlab.org> <Pine.LNX.4.21.0110142252270.6433-100000@Consulate.UFP.CX>
Followup to: <Pine.LNX.4.21.0110142252270.6433-100000@Consulate.UFP.CX>
By author: Riley Williams <rhw@MemAlpha.cx>
In newsgroup: linux.dev.kernel
>
> DD.MM.YYYY (European)
> MM/DD/YYYY (American)
> YYYY-MM-DD (Japanese)
>
> ...with the punctuation character specifying the one in use. I note that
> the dates as originally quoted above are clearly consistant with this
> standard, so see no problem myself.
>
> Personally, I prefer to use the DD-MMM-YYYY format myself, where MMM in
> the three-letter English abbreviation for the month in question, and
> there is thus no room for misreading it as something else.
>
YYYY-MM-DD is also unambiguous, and has the nice properties of being
(a) sortable and (b) language-independent.
-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:[~2001-10-15 0:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 2:12 Wireless Extension update Jean Tourrilhes
2001-10-09 16:22 ` Randy.Dunlap
2001-10-09 16:35 ` Jean Tourrilhes
2001-10-14 21:58 ` Riley Williams
2001-10-15 0:07 ` H. Peter Anvin [this message]
2001-10-15 19:26 ` Roeland Th. Jansen
2001-10-15 19:31 ` H. Peter Anvin
2001-10-15 21:02 ` Tobias Ringstrom
2001-10-15 0:08 ` H. Peter Anvin
[not found] ` <200110150008.RAA09482@cesium.transmeta.com>
2001-10-15 16:37 ` Jean Tourrilhes
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 2:12 Jean Tourrilhes
2000-12-20 0:59 Jean Tourrilhes
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='9qd9cp$977$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox