From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fix to tm2sec().
Date: Sun, 19 Jan 2003 13:48:32 -0800 [thread overview]
Message-ID: <2f9656f4670e3854b7c69c3f6e4e5aa2@mightycheese.com> (raw)
In-Reply-To: <200301192133.h0JLXIw14270@augusta.math.psu.edu>
> Actually, it's not, but if Dave's birthday falls on a particularly
> auspicious day, it could be all right. :-)
I think the problem would be that we'd need 64-bit ints to represent the
modern era.
-rob
next prev parent reply other threads:[~2003-01-19 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 20:43 Andrew Simmons
2003-01-19 21:33 ` Dan Cross
2003-01-19 21:48 ` rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-20 6:49 Andrew Simmons
2003-01-20 7:21 ` Russ Cox
2003-01-20 13:55 ` David Presotto
2003-01-18 23:03 Dan Cross
2003-01-18 23:07 ` David Presotto
2003-01-18 23:12 ` Dan Cross
2003-01-19 0:10 ` Russ Cox
2003-01-19 0:20 ` Dan Cross
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=2f9656f4670e3854b7c69c3f6e4e5aa2@mightycheese.com \
--to=rob@mightycheese.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).