aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2016-01-29 09:18:59 -0500
committerNick Mathewson <nickm@torproject.org>2016-01-29 09:18:59 -0500
commit5f7df92571ec5a2d1eddb257e22f5489acc4fc83 (patch)
tree9ef43ebc29ec04a5fe42f2411b3aa61ac2f643c8 /changes
parenta5bed4dab2f8521f744d5137e4f439b073c7e5e9 (diff)
downloadtor-5f7df92571ec5a2d1eddb257e22f5489acc4fc83.tar.gz
tor-5f7df92571ec5a2d1eddb257e22f5489acc4fc83.zip
Remove support for unsigned time_t
We've never actually tested this support, and we should probably assume it's broken. To the best of my knowledge, only OpenVMS has this, and even on OpenVMS it's a compile-time option to disable it. And I don't think we build on openvms anyway. (Everybody else seems to be working around the 2038 problem by using a 64-bit time_t, which won't expire for roughly 292 billion years.) Closes ticket 18184.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug181845
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/bug18184 b/changes/bug18184
new file mode 100644
index 0000000000..af493df75f
--- /dev/null
+++ b/changes/bug18184
@@ -0,0 +1,5 @@
+ o Removed platform support:
+ - Tor no longer attempts to support platforms where the "time_t" type
+ is unsigned. (To the best of our knowledge, only OpenVMS does this,
+ and Tor has never actually built on OpenVMS.) Closes ticket 18184.
+