From: "Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wireless Extension update
Date: Mon, 15 Oct 2001 19:26:47 +0000 [thread overview]
Message-ID: <20011015192647.A1769@grobbebol.xs4all.nl> (raw)
In-Reply-To: <3BC3243A.D3B48880@osdlab.org> <Pine.LNX.4.21.0110142252270.6433-100000@Consulate.UFP.CX> <9qd9cp$977$1@cesium.transmeta.com>
In-Reply-To: <9qd9cp$977$1@cesium.transmeta.com>; from hpa@zytor.com on Sun, Oct 14, 2001 at 05:07:53PM -0700
On Sun, Oct 14, 2001 at 05:07:53PM -0700, H. Peter Anvin wrote:
> YYYY-MM-DD is also unambiguous, and has the nice properties of being
> (a) sortable and (b) language-independent.
it only is unambiguous if you happen to know the format beforehand.
20011001 is ?
10 oct 2001 ?
01 jan 2001 ?
for the fun :
it's a known practise in aircraft complaint handling that there should
be a definition written at the place where complaints are signed off. if
there is no such thing, we always have to revert to the unambigous
dd-mmm-yyyy where the mmm is the three letter code for the month.
--
Grobbebol's Home | Don't give in to spammers. -o)
http://www.xs4all.nl/~bengel | Use your real e-mail address /\
Linux 2.4.10 (apic) SMP 466MHz/768 MB | on Usenet. _\_v
next prev parent reply other threads:[~2001-10-15 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 2:12 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
2001-10-15 19:26 ` Roeland Th. Jansen [this message]
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=20011015192647.A1769@grobbebol.xs4all.nl \
--to=roel@grobbebol.xs4all.nl \
--cc=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
all inboxes | Powered by JetHome®