From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Bryson <david@statichacks.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/4] replace unsinged long with time_t
Date: Thu, 6 Nov 2008 10:45:47 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811061042530.3419@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20081106183722.GL10996@eratosthenes.cryptobackpack.org>
On Thu, 6 Nov 2008, David Bryson wrote:
>
> 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 ?
It might be worth it to make the internal git time always be 64-bit.
It was kind of a long-term plan anyway: git doesn't really ever have to
work with dates in the future (and things like "approxidate()" actually
know that and use it to guess what date you must be talking about), so
even a 32-bit "unsigned long" is expected to work well until 2038, but at
_some_ point we'd need to guarantee 64-bit epoch times.
It just wasn't something I was in a huge hurry over. Others have to worry
about dates from the future long before wrap-around, git really doesn't.
But from a janitorial standpoint, I certainly wouldn't totally hate using
a known 64-bit type for dates.
Linus
next prev parent reply other threads:[~2008-11-06 18:47 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
2008-11-06 18:45 ` Linus Torvalds [this message]
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=alpine.LFD.2.00.0811061042530.3419@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=david@statichacks.org \
--cc=git@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