Mark locations that break in the year 2038
commit7d49619eb0403758cbbb0c6f18c6e164edad9fe2
authorShawn O. Pearce <spearce@spearce.org>
Wed, 17 Dec 2008 22:48:44 +0000 (17 14:48 -0800)
committerRobin Rosenberg <robin.rosenberg@dewire.com>
Sat, 20 Dec 2008 23:45:21 +0000 (21 00:45 +0100)
tree81e525843b7568a25ff6cb6fcc2ed0b5da89aa35
parent0ad1d82cb075930df8abe3fbc8457d71ae2214df
Mark locations that break in the year 2038

When the 32 bit timestamp rolls over in 2038 these spots in JGit
and everything that depends on them will break, unless we upgrade
them to use a 64 bit long before then. For now its too time and memory
intensive to use a full long here,but in another 10 years we should
have enough computing power that this is a moot point and we can upgrade
the code paths marked with by 'git grep 2038'.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
org.spearce.jgit/src/org/spearce/jgit/revwalk/RevCommit.java