From: David Bryson <david@statichacks.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/4] replace unsinged long with time_t
Date: Thu, 6 Nov 2008 10:37:22 -0800 [thread overview]
Message-ID: <20081106183722.GL10996@eratosthenes.cryptobackpack.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811061000430.3419@nehalem.linux-foundation.org>
Hi,
On Thu, Nov 06, 2008 at 10:13:46AM -0800 or thereabouts, Linus Torvalds wrote:
> So "time_t" really is a pretty damn worthless type. It's not _quite_ as
> broken as "socklen_t" (which is just a broken name for "int", and anybody
> who declares it to be anythign else is a total moron), but it's close.
I have always thought that time_t and similar were braindead, but hey
the Janitor page listed it as desireable so what do I know ?
> In theory, some platform might have a 64-but "unsigned long long" time_t
> even if the architecture is 32-bit (apparently windows used to do that if
> you included <time64.h>, for example), but since we wouldn't take
> advantage of that anyway, even then there is no real advantage.
Having a problem between 32 and 64 bit implementations does seem
undesireable.
http://git.or.cz/gitwiki/Janitor?action=info
Janitor wiki log says Pasky added the time_t conversion section. Care
to explain the reason for the request Pasky ?
Dave
next prev parent reply other threads:[~2008-11-06 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 17:48 [PATCH 0/4] replace unsinged long with time_t david
2008-11-06 17:48 ` [PATCH 1/4] Changed timestamps to time_t instead of unsigned david
2008-11-06 17:48 ` [PATCH 2/4] Changed timestamps to time_t in header files david
2008-11-06 17:48 ` [PATCH 3/4] Changed timestamps to time_t instead of unsigned long for approxidate() david
2008-11-06 17:48 ` [PATCH 4/4] Changed timestamps to time_t david
2008-11-06 18:13 ` [PATCH 0/4] replace unsinged long with time_t Linus Torvalds
2008-11-06 18:37 ` David Bryson [this message]
2008-11-06 18:45 ` Linus Torvalds
2008-11-06 21:04 ` Daniel Stenberg
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=20081106183722.GL10996@eratosthenes.cryptobackpack.org \
--to=david@statichacks.org \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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